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

mach: use signal kqueue instead of sigwait #22041

Merged
merged 1 commit into from
Mar 6, 2018
Merged

mach: use signal kqueue instead of sigwait #22041

merged 1 commit into from
Mar 6, 2018

Conversation

vtjnash
Copy link
Member

@vtjnash vtjnash commented May 23, 2017

this may help avoid getting spurious sigwait (InterruptException) notifications

@vtjnash vtjnash requested a review from yuyichao May 23, 2017 16:38
@StefanKarpinski
Copy link
Member

Probably helps performance too, no?

@vtjnash
Copy link
Member Author

vtjnash commented May 23, 2017

probably not

@StefanKarpinski
Copy link
Member

:sadface:

@vtjnash
Copy link
Member Author

vtjnash commented May 23, 2017

POSIX.1 specifies that the dispositions of any signals that are ignored or set to the default are left unchanged

hm, we're going to have to workaround that before merging

this may help avoid getting spurious sigwait notifications
@vtjnash vtjnash merged commit e542b28 into master Mar 6, 2018
@vtjnash vtjnash deleted the jn/sigwait-mach branch March 6, 2018 17:45
@iblislin
Copy link
Member

iblislin commented Mar 7, 2018

After this PR merged,
All master builds and PR builds on BSD CI failed:
e.g. https://freebsdci.julialang.org/#/builders/1/builds/8043

@iblislin
Copy link
Member

iblislin commented Mar 7, 2018

List of recent builds: https://freebsdci.julialang.org/#/builders/1

@StefanKarpinski
Copy link
Member

@vtjnash, did you rerun CI across the board before merging this ten months later?

vtjnash added a commit that referenced this pull request Dec 4, 2019
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.
vtjnash added a commit that referenced this pull request Dec 11, 2019
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.
KristofferC pushed a commit that referenced this pull request Apr 11, 2020
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants