You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a testitem hits the timeout limit, we print out whatever logs it produced and then kill the worker, but we don't print out any info about what the worker was actually doing, which makes it hard to know e.g. if the testitem was deadlocked.
It would be helpful to collect and print out a CPU profile by sending a SIGINFO/SIGUSR1 to the process before sending the SIGTERM
Alternatively, we could dump julia task backtraces and/or CPU stacktraces.
The text was updated successfully, but these errors were encountered:
When a testitem hits the timeout limit, we print out whatever logs it produced and then kill the worker, but we don't print out any info about what the worker was actually doing, which makes it hard to know e.g. if the testitem was deadlocked.
It would be helpful to collect and print out a CPU profile by sending a SIGINFO/SIGUSR1 to the process before sending the SIGTERM
Alternatively, we could dump julia task backtraces and/or CPU stacktraces.
The text was updated successfully, but these errors were encountered: