-
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
Investigate flaky parallel/test-tls-socket-close on Raspberry Pi #11912
Comments
If we can't get rid of |
I am able to cause this and several other timing-related problems by running the test under load. The other problems seem more common but every once in a while I get something like this: tools/test.py -j 32 --repeat 32 test/parallel/test-tls-socket-close.js
=== release test-tls-socket-close ===
Path: parallel/test-tls-socket-close
events.js:184
throw er; // Unhandled 'error' event
^
Error: read ECONNRESET
at exports._errnoException (util.js:1028:11)
at TLSWrap.onread (net.js:605:26)
Command: out/Release/node /Users/trott/io.js/test/parallel/test-tls-socket-close.js
[00:01|% 100|+ 31|- 1]: Done EDIT: The |
Replace timer/timeout race with event-based ordering, eliminating test flakiness. Fixes: nodejs#11912
Proposed fix in #11921 |
Replace timer/timeout race with event-based ordering, eliminating test flakiness. PR-URL: nodejs/node#11921 Fixes: nodejs/node#11912 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
https://ci.nodejs.org/job/node-test-binary-arm/6752/RUN_SUBSET=3,label=pi1-raspbian-wheezy/console
@nodejs/testing @jBarz
The text was updated successfully, but these errors were encountered: