-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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 test test-child-process-fork-net2 #2669
Comments
I am unable to reproduce this on OS X, SmartOS or Ubuntu. With the latest master build, I ran the following and 100/100 tests run on all three tested environments:
Also, what about a |
Also, let me know if I messed up the reproduction recipe. |
FWIW, I haven't been able to reproduce this locally on OSX and Linux either. |
Good to hear. :) I'll keep moving down the list and updating with either a PR or a similar update to this one. |
Thanks. FYI, we are coming up with a Jenkins job to stress individual tests in CI, so we can quickly verify if a test is really flaky or not. |
Cool. I've got scripts on *nix and Windows to run similar tests like above. If I can help, let me know. |
Given that the flakiness has not been reproduced, I'm going to close this. Anyone should feel absolutely free to re-open with no hesitation at all if you think I'm being rash or if the issue does re-appear. |
Sounds good. Verified NOT flaky in CI: https://ci.nodejs.org/job/node-stress-single-test/4/nodes=smartos14-64/console |
Failed on SmartOS in this run: https://ci.nodejs.org/job/node-test-commit-other/423/nodes=smartos14-64/
Was deemed not related to the change in that PR: #2402
The text was updated successfully, but these errors were encountered: