-
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
Intermittent failures in test-process-exec-argv #6480
Comments
addaleax
added
test
Issues and PRs related to the tests.
process
Issues and PRs related to the process subsystem.
labels
Apr 29, 2016
2 tasks
I could reproduce the issue in |
will do |
Running in a long loop on the machine we saw the failure as we speak. So far looks good but want to let it run through at least several thousand iterations before comfirming |
Ok 6000+ runs without a failure with that patch so looks good. |
santigimeno
added a commit
to santigimeno/node
that referenced
this issue
May 12, 2016
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]>
evanlucas
pushed a commit
that referenced
this issue
May 17, 2016
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]>
santigimeno
added a commit
to santigimeno/node
that referenced
this issue
Jun 3, 2016
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]>
MylesBorins
pushed a commit
that referenced
this issue
Jun 4, 2016
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]>
MylesBorins
pushed a commit
that referenced
this issue
Jun 24, 2016
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]>
MylesBorins
pushed a commit
that referenced
this issue
Jun 24, 2016
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]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We see this test fail intermittently (about 0.4% of the time on one of our machines) with:
We believe the cause is related to the issue being discussed here: #6456
Opening this issue as the outcome of #6456 may or may not resolve the failing test depending on what's decided as the right way forward so we need to track this failure to make sure the test is either fixed by what we do for 6456 or that the test is updated to remove the dependency on the process exit timing if what we do for 6456 does not resolve the issue
The text was updated successfully, but these errors were encountered: