-
Notifications
You must be signed in to change notification settings - Fork 478
dispatch_io pipe close test #476
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
Conversation
|
@swift-ci test macOS |
|
@swift-ci please test |
|
@weissi can you provide a patch that fixes this as well? |
|
@MadCoder @ktopley-apple this demonstrates a problem that we have been hitting on the linux pull request bots in c (so we can run it unconditionally in all the CI with/without swift). I don't know if it effects Darwin. |
It does not affect Darwin because the bug is in the way Dispatch uses |
Sorry, that fix isn't trivial and I really don't know enough about the dispatch implementation there. |
|
#477 is a tentative fix which makes this test pass. Thanks for providing this :) |
|
@compnerd cross repo PR testing only works cross repo ; ). |
If epoll_wait() reports EPOLLHUP, we must respond immediately and unregister the event or else Dispatch will go into a spinloop. This makes dispatch_io_pipe_close (swiftlang#476) pass on Linux with identical output to Darwin.
|
I created a combined PR for this with the fix. It is going through testing now. I am going to close this so there isn't confusion and we keep the record that it failed. The important part from the relevant log: |
If epoll_wait() reports EPOLLHUP, we must respond immediately and unregister the event or else Dispatch will go into a spinloop. This makes dispatch_io_pipe_close (swiftlang#476) pass on Linux with identical output to Darwin. (cherry picked from commit ffc7133)
If epoll_wait() reports EPOLLHUP, we must respond immediately and unregister the event or else Dispatch will go into a spinloop. This makes dispatch_io_pipe_close (#476) pass on Linux with identical output to Darwin. Signed-off-by: Kim Topley <ktopley@apple.com>
this is a test that documents the problem seen in