[syscall] Accept O_NONBLOCK flag in pipe2#26501
Conversation
sbc100
left a comment
There was a problem hiding this comment.
Can you update the test for pipe2 to include this flag?
sbc100
left a comment
There was a problem hiding this comment.
lgtm otherwise! Thanks for working on this
|
Added a test |
ae16cf7 to
b91ca8d
Compare
Head branch was pushed to by a user without write access
b91ca8d to
2183911
Compare
|
For the codesize test updates you will want to do |
2183911 to
e25ce23
Compare
|
From https://github.com/emscripten-core/emscripten/actions/runs/23765785637/job/69244759709?pr=26501: This looks weird to me |
Hmm.. yes that does looks strange. That can happen sometimes when the script doesn't know how to parse the json file in question correctly. Are you able to run If you are not able to do that, and you have tried |
|
Regarding the codesize expectations, you may also find this Dockerfile relevant: The issue is that gzip-compressed data may not be bit-identical across different zlib versions (it looks like you're using zlib-ng as well). |
Head branch was pushed to by a user without write access
e25ce23 to
99c3bc8
Compare
pipe2 only accepted O_CLOEXEC, rejecting O_NONBLOCK with ENOTSUP. Accept O_NONBLOCK and set it on the created pipe streams. This is needed by GLib's GWakeup which uses pipe2(fds, O_CLOEXEC | O_NONBLOCK).
99c3bc8 to
f7a572d
Compare
I used the docker file to regenerate with and it is still failing |
|
I doubt there are docker images available for the tot build which is what you need to be rebasing against. |
I built it myself based on this dockerfile Let me rebuild in case it was bad timing 🤷 |
|
I pushed a change to this branch with the updated codesizes. |
pipe2 only accepted O_CLOEXEC, rejecting O_NONBLOCK with ENOTSUP. Accept O_NONBLOCK and set it on the created pipe streams, it is a no-op in practice, but there is no reason to not allow it.