-
Notifications
You must be signed in to change notification settings - Fork 30k
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
test: refactor test-http-destroyed-socket-write2 #4970
Conversation
Looks like there's a minor lint issue to fix:
|
Ouch, sorry about that. Updated. |
Because of its history of flakiness, it might be a good idea to run a stress test for this on AIX and Windows. It shouldn't stop this from landing, but it might also be worth experimenting after this lands to see if |
I don't think we have AIX in CI yet. I kicked off a stress test on Windows 10. https://ci.nodejs.org/job/node-stress-single-test/395/nodes=win10/ |
LGTM if CI is green. |
LGTM |
@santigimeno I'd like to land this, but I want to make sure we have a pretty recent CI run so I'd like to run it again. Can you rebase against master and force push? |
Remove the limit of requests to be sent (128) as in some conditions it was reached without the `error` event being fired, causing the test to fail. Remove the initial timeout. Remove some variables used to check the validity of the test and replace them with `common.mustCall` and `common.fail` calls.
@Trott done |
CI is green. LGTM. Would be interested to know if this fixes the issue for @thealphanerd too. |
Remove the limit of requests to be sent (128) as in some conditions it was reached without the `error` event being fired, causing the test to fail. Remove the initial timeout. Remove some variables used to check the validity of the test and replace them with `common.mustCall` and `common.fail` calls. PR-URL: nodejs#4970 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Roman Klauke <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Landed in b920d45 |
Remove the limit of requests to be sent (128) as in some conditions it was reached without the `error` event being fired, causing the test to fail. Remove the initial timeout. Remove some variables used to check the validity of the test and replace them with `common.mustCall` and `common.fail` calls. PR-URL: #4970 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Roman Klauke <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Remove the limit of requests to be sent (128) as in some conditions it was reached without the `error` event being fired, causing the test to fail. Remove the initial timeout. Remove some variables used to check the validity of the test and replace them with `common.mustCall` and `common.fail` calls. PR-URL: #4970 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Roman Klauke <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Remove the limit of requests to be sent (128) as in some conditions it was reached without the `error` event being fired, causing the test to fail. Remove the initial timeout. Remove some variables used to check the validity of the test and replace them with `common.mustCall` and `common.fail` calls. PR-URL: #4970 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Roman Klauke <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Remove the limit of requests to be sent (128) as in some conditions it was reached without the `error` event being fired, causing the test to fail. Remove the initial timeout. Remove some variables used to check the validity of the test and replace them with `common.mustCall` and `common.fail` calls. PR-URL: #4970 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Roman Klauke <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Remove the limit of requests to be sent (128) as in some conditions it
was reached without the
error
event being fired, causing thetest to fail.
Remove the initial timeout.
Remove some variables used to check the validity of the test and replace
them with
common.mustCall
andcommon.fail
calls.The error I was getting from time to time in
OS X
was: