-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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 test-process-exec-argv flakiness #6575
Conversation
LGTM |
LGTM. CI is green except for Jenkins issues on armv8-ubuntu1404. |
LGTM |
12e8968
to
ed982b1
Compare
6000+ runs on test-process-exec-argv on a machine were we'd seen it fail 0.4% of the time without this change so LGTM |
By the way, the upcoming libuv release (libuv/libuv#867) contains a fix that quite possibly also resolves this. |
@bnoordhuis should this be merged anyway or just wait for the fix? |
It would be interesting to find out if it fixes the test but don't let it block you. |
Wait for the `close` event before parsing the child stdout output. Fixes: nodejs#6480 PR-URL: nodejs#6575 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michael Dawson <[email protected]>
ed982b1
to
80481da
Compare
CI green expect unrelated failures: https://ci.nodejs.org/job/node-test-pull-request/2605/ |
Wait for the `close` event before parsing the child stdout output. Fixes: #6480 PR-URL: #6575 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michael Dawson <[email protected]>
Landed in dffafde. Thanks! |
Wait for the `close` event before parsing the child stdout output. Fixes: #6480 PR-URL: #6575 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michael Dawson <[email protected]>
This does not land cleanly in LTS. Added dont-land label. Please feel free to manually backport |
@thealphanerd PR with the backport here: #7128 |
Wait for the `close` event before parsing the child stdout output. Fixes: nodejs#6480 Ref: nodejs#6575 PR-URL: nodejs#7128 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michael Dawson <[email protected]>
Wait for the `close` event before parsing the child stdout output. Fixes: #6480 Ref: #6575 PR-URL: #7128 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michael Dawson <[email protected]>
Wait for the `close` event before parsing the child stdout output. Fixes: #6480 Ref: #6575 PR-URL: #7128 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michael Dawson <[email protected]>
Wait for the `close` event before parsing the child stdout output. Fixes: #6480 Ref: #6575 PR-URL: #7128 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michael Dawson <[email protected]>
Checklist
Affected core subsystem(s)
test
Description of change
Wait for the
close
event before parsing the child stdout output.Fixes: #6480
I was able to reproduce the error reported in #6480 in my
OS X
box. This change fixed the issue.