8.12-m02-int: Explain a test [TIMEOUT] instead of killing it silently (#15879)
- Redis: 18 events in the last 90 days
- Redis: 17th Release in the last 90 days
- Previous: 10 days earlier · 8.10.2
What happened
A hung test run tells us almost nothing today. When no client has made progress for --timeout seconds, test_server_cron prints the clients' last reported state, SIGKILLs every server via force_kill_all_servers and exits; --dump-logs only fires for a failed or excepted test, never for a timeout. So a 20-minute hang costs a whole CI run and produces a few lines. Collect the evidence before tearing the run down: Crash-…
Summary assembled by rule from the sources below