Uh oh!
There was an error while loading. Please reload this page.
test: fix flaky child-process-fork-regr-gh-2847 - #4442
Conversation
indutny
commented
Dec 27, 2015
I think I'm fine with this change as long as it fails on unpatched node.js (i.e. before this regression was fixed). |
There was a problem hiding this comment.
Maybe wrap this in an if (common.isWindows) so it only applies to the affected OS? Or not. Just throwing it out there.
mscdex
commented
Dec 27, 2015
@indutny Yes, the tests still properly fail before the fix (e.g. node v4.1.1). |
indutny
commented
Dec 27, 2015
Ok, then one nit by @Trott . Otherwise LGTM |
Windows would die with ECONNRESET most times when running this particular test. This commit makes handling these errors more tolerable.
af005ce to
57a400eComparemscdex
commented
Dec 28, 2015
mscdex
commented
Dec 28, 2015
Whoa, that was weird... suddenly all kinds of seemingly unrelated issues on Windows. |
mscdex
commented
Dec 28, 2015
I re-ran them all again and this time it's all green: https://ci.nodejs.org/job/node-test-pull-request/1086/ I'm guessing the previous time it was something CI related? |
jbergstroem
commented
Dec 28, 2015
@mscdex yeah, not sure what was up with the windows slaves last run. |
Trott
commented
Dec 28, 2015
Green! Another all green!!!! \o/ |
mscdex
commented
Dec 28, 2015
mscdex
commented
Dec 29, 2015
Stress test is green! \o/ |
jbergstroem
commented
Dec 29, 2015
Trott
commented
Dec 29, 2015
LGTM |
Windows would die with ECONNRESET most times when running this particular test. This commit makes handling these errors more tolerable. PR-URL: #4442 Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
mscdex
commented
Dec 29, 2015
Landed in 30c0062. |
Windows would die with ECONNRESET most times when running this particular test. This commit makes handling these errors more tolerable. PR-URL: nodejs#4442 Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Windows would die with ECONNRESET most times when running this particular test. This commit makes handling these errors more tolerable. PR-URL: #4442 Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Windows is still sometimes failing with ECONNRESET. Bring back the handling of this error as was initially introduced in PR nodejs#4442.
Windows is still sometimes failing with ECONNRESET. Bring back the handling of this error as was initially introduced in PR nodejs#4442. PR-URL: nodejs#5179 Reviewed-By: Rich Trott <rtrott@gmail.com> Fixes: nodejs#3635
Windows would die with ECONNRESET most times when running this particular test. This commit makes handling these errors more tolerable. PR-URL: #4442 Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Windows would die with ECONNRESET most times when running this particular test. This commit makes handling these errors more tolerable. PR-URL: nodejs#4442 Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Windows would die with ECONNRESET most times when running this particular test. This commit makes handling these errors more tolerable. PR-URL: nodejs#4442 Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Windows is still sometimes failing with ECONNRESET. Bring back the handling of this error as was initially introduced in PR nodejs#4442. PR-URL: nodejs#5179 Reviewed-By: Rich Trott <rtrott@gmail.com> Fixes: nodejs#3635
Windows would die with ECONNRESET most times when running this particular test. This commit makes handling these errors more tolerable. PR-URL: nodejs#4442 Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>

Windows would die with ECONNRESET most times when running this particular test. This commit makes handling these errors more tolerable.
I'm not sure if the error handling logic is 100% correct here. Is silencing ECONNRESET errors on server-side sockets ever acceptable, or are those particular errors relevant to this test?
/cc @mhdawson@jasnell@indutny@trevnorris