-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Assertion failure in Scheduler code #55235
Comments
This test runs inside CC: @DilumAluthge who might know. |
You missed the assertion text in your copy. It is this:
When a signal causes a thread to resume, we need to also force it back into the |
Ah, OK. Thanks for the clarification. Suspect it's fine to close then? |
Yeah, if you follow the link to Buildkite, you can click on the "Artifacts" tab, and then you can download the It might be split across multiple parts that you need to combine back together. |
This error is happening with a high rate lately. |
Fixes #55235 Disables the assertion failure in the scheduler, so that we are more likely to be able to report the underlying failure and run atexit handlers successfully. This should clean up some of the error messages that occur on timeout. ``` julia> sleep(5) ^\ [89829] signal 3: Quit: 3 in expression starting at REPL[1]:1 kevent at /usr/lib/system/libsystem_kernel.dylib (unknown line) unknown function (ip: 0x0) Allocations: 830502 (Pool: 830353; Big: 149); GC: 1 Quit: 3 ```
Fixes JuliaLang#55235 Disables the assertion failure in the scheduler, so that we are more likely to be able to report the underlying failure and run atexit handlers successfully. This should clean up some of the error messages that occur on timeout. ``` julia> sleep(5) ^\ [89829] signal 3: Quit: 3 in expression starting at REPL[1]:1 kevent at /usr/lib/system/libsystem_kernel.dylib (unknown line) unknown function (ip: 0x0) Allocations: 830502 (Pool: 830353; Big: 149); GC: 1 Quit: 3 ```
See https://buildkite.com/julialang/julia-master/builds/38431#0190e57f-77e8-461e-afd1-be9abc0297f8:
This happened in #55233, which is basically a NFC and doesn't change anything in the scheduler, so I think it's unlikely to be related to the PR.
The text was updated successfully, but these errors were encountered: