-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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: improve test-gc-http-client-timeout #23184
Conversation
* decrease number of requests 500 -> 300 * extract 'cb' to a file-local function This should make test more reliable and less resource intensive.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! :)
@addaleax @BridgeAR @thefourtheye what do you think of this suggestion
I mentioned in the first post? Edit: resume CI: https://ci.nodejs.org/job/node-test-pull-request/17552/ |
Landed in 69a422b. |
* decrease number of requests 500 -> 300 * extract 'cb' to a file-local function This should make test more reliable and less resource intensive. PR-URL: #23184 Refs: #23066 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Sakthipriyan Vairamani <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: James M Snell <[email protected]>
@lundibundi That suggestion can be done separately. Get a PR up, let's see what people think. |
* decrease number of requests 500 -> 300 * extract 'cb' to a file-local function This should make test more reliable and less resource intensive. PR-URL: #23184 Refs: #23066 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Sakthipriyan Vairamani <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: James M Snell <[email protected]>
* decrease number of requests 500 -> 300 * extract 'cb' to a file-local function This should make test more reliable and less resource intensive. PR-URL: #23184 Refs: #23066 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Sakthipriyan Vairamani <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: James M Snell <[email protected]>
This should make test more reliable and less resource intensive.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAlso, by moving for-loop of getall calls into the server callback I managed to run this with '-j 32 --repeat 1920' on a 4 core, 8 thread machine. Though this removes 'surefire' timeouts (due to a server being unavailable) this test will still get the timeouts due to the sheer amount of requests being made. Therefore if it's okay I'll make the change.
Refs: #23066
(not fixes as this still fails in parallel on '-j 32 --repeat 1920' locally)