test: fix flaky child-process-fork-regr-gh-2847#4442
test: fix flaky child-process-fork-regr-gh-2847#4442mscdex wants to merge 1 commit intonodejs:masterfrom
Conversation
|
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.
|
@indutny Yes, the tests still properly fail before the fix (e.g. node v4.1.1). |
|
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
57a400e
Compare
|
Whoa, that was weird... suddenly all kinds of seemingly unrelated issues on Windows. |
|
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? |
|
@mscdex yeah, not sure what was up with the windows slaves last run. |
|
Green! Another all green!!!! \o/ |
|
Stress test is green! \o/ |
|
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>
|
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