| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Stress test for this version of the test, expected to show zero failures: https://ci.nodejs.org/job/node-stress-single-test/545/nodes=smartos14-32/console Stress test for current version on master, showing failures: https://ci.nodejs.org/job/node-stress-single-test/528/nodes=smartos14-32/console |
Sorry, something went wrong.
Sorry, something went wrong.
How is it done? |
Sorry, something went wrong.
|
@santigimeno wrote:
|
Sorry, something went wrong.
|
/cc @nodejs/testing |
Sorry, something went wrong.
Sorry, something went wrong.
|
Bump. @nodejs/collaborators |
Sorry, something went wrong.
|
Still fishing for an LGTM on this from an onboarded collaborator. Maybe @mscdex who reported the problem? Or @jasnell who LGTMed a similar fix in another test? Or @indutny who reviewed a PR for a more generalized fix that helps other tests but not necessarily ones with lots of connections like this one? |
Sorry, something went wrong.
|
Why doesn't more generalized fix do not help here? |
Sorry, something went wrong.
There was a problem hiding this comment.
Please skip additional parens here.
Sorry, something went wrong.
There was a problem hiding this comment.
Please skip additional parens here.
Additional parens removed, branch rebased, force pushed. Will run CI one more time.
There's a build-in lint rule to catch extra parentheses, Alas, enabling it flags 315 instances in the code base. Probably not worth the churn. I might look more closely at it, though...
Sorry, something went wrong.
|
Anyway, if it helps - LGTM |
Sorry, something went wrong.
|
@indutny asked:
The more generalized fix retries the test one time if it's SmartOS and failed due to ECONNREFUSED. That works well for tests that open just a few connections because the bug seems to crop up once every few hundred connections or so. However, for tests that open dozens or hundreds of connections, one retry may not be enough. So, for this and for one other test, we ignore ECONNREFUSED on SmartOS and try the connection again within the test itself. |
Sorry, something went wrong.
There is a known issue with SmartOS that is generally worked around in `tools/test.py`. However, a more robust workaround is required for some tests that open many network connections. `test-http-regr-nodejsgh-2928` is one such test. Fixes: nodejs#5445 Refs: nodejs#3941 PR-URL: nodejs#5454
|
Hopefully gratuitous CI: https://ci.nodejs.org/job/node-test-pull-request/1796/ |
Sorry, something went wrong.
There is a known issue with SmartOS that is generally worked around in `tools/test.py`. However, a more robust workaround is required for some tests that open many network connections. `test-http-regr-nodejsgh-2928` is one such test. Fixes: nodejs#5445 Refs: nodejs#3941 PR-URL: nodejs#5454 Reviewed-By: Fedor Indutny <fedor@indutny.com>
There is a known issue with SmartOS that is generally worked around in `tools/test.py`. However, a more robust workaround is required for some tests that open many network connections. `test-http-regr-gh-2928` is one such test. Fixes: #5445 Refs: #3941 PR-URL: #5454 Reviewed-By: Fedor Indutny <fedor@indutny.com>
There is a known issue with SmartOS that is generally worked around in `tools/test.py`. However, a more robust workaround is required for some tests that open many network connections. `test-http-regr-gh-2928` is one such test. Fixes: #5445 Refs: #3941 PR-URL: #5454 Reviewed-By: Fedor Indutny <fedor@indutny.com>
There is a known issue with SmartOS that is generally worked around in `tools/test.py`. However, a more robust workaround is required for some tests that open many network connections. `test-http-regr-gh-2928` is one such test. Fixes: #5445 Refs: #3941 PR-URL: #5454 Reviewed-By: Fedor Indutny <fedor@indutny.com>
The flakiness issue for test-http-regr-nodejsgh-2928 on SmartOS was resolved in late February in nodejs#5454. This change removes its flaky designation in sequential.status.
The flakiness issue for test-http-regr-nodejsgh-2928 on SmartOS was resolved in late February in nodejs#5454. This change removes its flaky designation in sequential.status. PR-URL: nodejs#6540 Reviewed-By: James M Snell <jasnell@gmail.com>
| Back | FazBrowse Home | New Git URL |
There is a known issue with SmartOS that is generally worked around
in tools/test.py. However, a more robust workaround is required for
some tests that open many network connections.
test-http-regr-gh-2928 is one such test.
Fixes: #5445
Refs: #3941