-
Notifications
You must be signed in to change notification settings - Fork 15
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
Set JULIA_TEST_TIMEOUT_SIGNUM=3 #165
base: main
Are you sure you want to change the base?
Conversation
Converting to draft so we don't accidentally merge while we still have a "do not merge" commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any particular reason to use SIGSEGV instead of SIGQUIT?
Nope, that's a great idea. |
We're waiting on this until I understand signal handling better, and am able to reliably trigger core dumps on all platforms. |
f31b72e
to
e88884b
Compare
Okay, so we made some progress by identifying that macOS was resetting our coredump config on reboot. I think we also need to change by to using SIGSEGV, because as Jameson said on Slack, Julia intercepts SIGQUIT, and thus SIGQUIT won't trigger core dumps. |
368ff24
to
03a5c57
Compare
@staticfloat Can we try to get this in? |
With JuliaLang/julia#47234, I think that if the SIGSEGV is sent by us via |
SIGQUIT generally causes a process to coredump, so let's use that as the termination signal throughout our test suite. X-ref: JuliaLang/julia#45864
03a5c57
to
5d5bfd4
Compare
Let's try to get some coredumps from our timeouts