-
-
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
mach: use signal kqueue instead of sigwait #22041
Conversation
Probably helps performance too, no? |
probably not |
:sadface: |
hm, we're going to have to workaround that before merging |
this may help avoid getting spurious sigwait notifications
4cdbecf
to
38f834b
Compare
After this PR merged, |
List of recent builds: https://freebsdci.julialang.org/#/builders/1 |
@vtjnash, did you rerun CI across the board before merging this ten months later? |
I am observing this value get set to EINTR sometimes on Linux. It is not generally supposed to do that (though not prohibited either). That is causing us to sometimes drop signals (usually SIGINT). Since we just need this code for Darwin (ref #17626, #22041, #20174), we can remove this from everywhere else.
I am observing this value get set to EINTR sometimes on Linux. It is not generally supposed to do that (though not prohibited either). That is causing us to sometimes drop signals (usually SIGINT). Since we just need this code for Darwin (ref #17626, #22041, #20174), we can remove this from everywhere else.
I am observing this value get set to EINTR sometimes on Linux. It is not generally supposed to do that (though not prohibited either). That is causing us to sometimes drop signals (usually SIGINT). Since we just need this code for Darwin (ref #17626, #22041, #20174), we can remove this from everywhere else.
this may help avoid getting spurious sigwait (InterruptException) notifications