Closed
Description
If a test hangs, the output of test-run will look like this:
No output during 10 seconds. List of workers not reporting the status: [1]; Will abort after 120 seconds without output.
No output during 20 seconds. List of workers not reporting the status: [1]; Will abort after 120 seconds without output.
No output during 30 seconds. List of workers not reporting the status: [1]; Will abort after 120 seconds without output.
No output during 40 seconds. List of workers not reporting the status: [1]; Will abort after 120 seconds without output.
No output during 50 seconds. List of workers not reporting the status: [1]; Will abort after 120 seconds without output.
No output during 60 seconds. List of workers not reporting the status: [1]; Will abort after 120 seconds without output.
No output during 70 seconds. List of workers not reporting the status: [1]; Will abort after 120 seconds without output.
No output during 80 seconds. List of workers not reporting the status: [1]; Will abort after 120 seconds without output.
No output during 90 seconds. List of workers not reporting the status: [1]; Will abort after 120 seconds without output.
No output during 100 seconds. List of workers not reporting the status: [1]; Will abort after 120 seconds without output.
No output during 110 seconds. List of workers not reporting the status: [1]; Will abort after 120 seconds without output.
No output during 120 seconds. List of workers not reporting the status: [1]; Will abort after 120 seconds without output.
[Main process] No output from workers. It seems that we hang. Send SIGKILL to workers; exiting...
---------------------------------------------------------------------------------
Count of didn't processed tasks: 1
That is, looking at the output it is impossible to say what happened. It would be great if test-run printed the output of hung tests (diff or tap result).