-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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-cluster-shared-leak #4510
Conversation
Wait for worker2 to come online before doing anything that might result in an EPIPE. Fixes flakiness of test on Windows. Fixes: nodejs#3956
CI: https://ci.nodejs.org/job/node-test-pull-request/1131/ All green! \o/ |
Confirmed that the test still triggers an AssertionError in Node 4.2.1, so it still tests what it was originally written to test. |
Stress tests: With this fix, 9999 runs and no errors: https://ci.nodejs.org/job/node-stress-single-test/288/nodes=win2012r2-1p/console Without, 9999 runs and four errors: https://ci.nodejs.org/job/node-stress-single-test/289/nodes=win2012r2-1p/console |
LGTM |
1 similar comment
LGTM |
Wait for worker2 to come online before doing anything that might result in an EPIPE. Fixes flakiness of test on Windows. Fixes: nodejs#3956 PR-URL: nodejs#4510 Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: James M Snell<[email protected]>
Landed in 063c9f6 |
Wait for worker2 to come online before doing anything that might result in an EPIPE. Fixes flakiness of test on Windows. Fixes: nodejs#3956 PR-URL: nodejs#4510 Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: James M Snell<[email protected]>
@Trott It looks like this is happening still, at least on win10 now: https://ci.nodejs.org/job/node-test-binary-windows/506/RUN_SUBSET=0,VS_VERSION=vs2015,label=win10/console |
@mscdex Unfortunately, yes. And unfortunately, I can't seem to replicate the failure in the stress test. Which is kind of troubling. Anyway, see #4476 (comment) and #4476 (comment) |
@Trott this one needs to be manually backported too :( |
@thealphanerd This will apply cleanly if you land #4421 first. |
Wait for worker2 to come online before doing anything that might result in an EPIPE. Fixes flakiness of test on Windows. Fixes: #3956 PR-URL: #4510 Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: James M Snell<[email protected]>
Wait for worker2 to come online before doing anything that might result in an EPIPE. Fixes flakiness of test on Windows. Fixes: #3956 PR-URL: #4510 Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: James M Snell<[email protected]>
Wait for worker2 to come online before doing anything that might result in an EPIPE. Fixes flakiness of test on Windows. Fixes: nodejs#3956 PR-URL: nodejs#4510 Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: James M Snell<[email protected]>
Wait for worker2 to come online before doing anything that might result in an EPIPE. Fixes flakiness of test on Windows. Fixes: nodejs#3956 PR-URL: nodejs#4510 Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: James M Snell<[email protected]>
Wait for worker2 to come online before doing anything that might result in an EPIPE. Fixes flakiness of test on Windows. Fixes: nodejs#3956 PR-URL: nodejs#4510 Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: James M Snell<[email protected]>
Wait for worker2 to come online before doing anything that might result
in an EPIPE. Fixes flakiness of test on Windows.
Fixes: #3956