-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
test: fix flaky test-http2-respond-file-error-pipe-offset #36305
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Can't we use a UNIX socket instead? |
I'm under the impression that the test is specifically for an issue involving pipes, but I could be wrong. /ping @addaleax |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is fine, as would be using a socket. The important thing is that the target file is not seekable.
Landed in f178c5a |
Fixes: #35881 PR-URL: #36305 Reviewed-By: Anna Henningsen <[email protected]>
Fixes: nodejs#35881 PR-URL: nodejs#36305 Reviewed-By: Anna Henningsen <[email protected]>
Fixes: #35881 PR-URL: #36305 Reviewed-By: Anna Henningsen <[email protected]>
Fixes: #35881
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes