Skip to content

Conversation

@lundibundi
Copy link
Member

@lundibundilundibundi commented Sep 30, 2018

  • decrease number of requests 500 -> 300
  • extract 'cb' to a file-local function

This should make test more reliable and less resource intensive.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • commit message follows commit guidelines

Also, 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)

* decrease number of requests 500 -> 300 * extract 'cb' to a file-local function This should make test more reliable and less resource intensive.
@lundibundilundibundi self-assigned this Sep 30, 2018
@nodejs-github-botnodejs-github-bot added the test Issues and PRs related to the tests. label Sep 30, 2018
@lundibundilundibundi changed the title test: harden test-gc-http-client-timeouttest: improve test-gc-http-client-timeoutSep 30, 2018
Copy link
Member

@addaleaxaddaleax left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! :)

@lundibundi
Copy link
MemberAuthor

@lundibundilundibundi added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Oct 1, 2018
@lundibundi
Copy link
MemberAuthor

lundibundi commented Oct 1, 2018

@addaleax@BridgeAR@thefourtheye what do you think of this suggestion

Also, 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.

I mentioned in the first post?

Edit: resume CI: https://ci.nodejs.org/job/node-test-pull-request/17552/

@danbev
Copy link
Contributor

Landed in 69a422b.

@danbevdanbev closed this Oct 4, 2018
danbev pushed a commit that referenced this pull request Oct 4, 2018
* 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]>
@thefourtheye
Copy link
Contributor

@lundibundi That suggestion can be done separately. Get a PR up, let's see what people think.

targos pushed a commit that referenced this pull request Oct 5, 2018
* 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]>
@targostargos mentioned this pull request Oct 7, 2018
jasnell pushed a commit that referenced this pull request Oct 17, 2018
* 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]>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.testIssues and PRs related to the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

@lundibundi@nodejs-github-bot@danbev@thefourtheye@jasnell@addaleax@BridgeAR