Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Print profile dump before killing worker when we timeout #105

Closed
nickrobinson251 opened this issue Aug 7, 2023 · 0 comments · Fixed by #120
Closed

Print profile dump before killing worker when we timeout #105

nickrobinson251 opened this issue Aug 7, 2023 · 0 comments · Fixed by #120
Labels
new feature A feature we would like to add

Comments

@nickrobinson251
Copy link
Collaborator

nickrobinson251 commented Aug 7, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new feature A feature we would like to add
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant