You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Investigate flaky test test-child-process-fork-net2 #2669
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:
time (OK=0; NOK=0; for i in `seq 100`; do ./node test/parallel/test-child-process-fork-net2.js && OK=$(($OK+1)) || NOK=$(($NOK+1)); echo "$i OK: $OK NOT OK: $NOK"; done)
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.
Activity
test: test-child-process-fork-net2 is flaky
whitlockjc commentedon Oct 20, 2015
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
smartoslabel for this?whitlockjc commentedon Oct 20, 2015
Also, let me know if I messed up the reproduction recipe.
bnoordhuis commentedon Oct 20, 2015
FWIW, I haven't been able to reproduce this locally on OSX and Linux either.
whitlockjc commentedon Oct 20, 2015
Good to hear. :) I'll keep moving down the list and updating with either a PR or a similar update to this one.
orangemocha commentedon Oct 21, 2015
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.
whitlockjc commentedon Oct 21, 2015
Cool. I've got scripts on *nix and Windows to run similar tests like above. If I can help, let me know.
Trott commentedon Nov 15, 2015
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.
orangemocha commentedon Nov 17, 2015
Sounds good. Verified NOT flaky in CI: https://ci.nodejs.org/job/node-stress-single-test/4/nodes=smartos14-64/console