Skip to content
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: speed up test-net-reconnect-error #7886

Closed
wants to merge 1 commit into from
Closed

Conversation

Trott
Copy link
Member

@Trott Trott commented Jul 27, 2016

Checklist
  • make -j4 test (UNIX), or vcbuild test nosign (Windows) passes
  • commit message follows commit guidelines
Affected core subsystem(s)

test net

Description of change

The test takes 50 seconds on some of the project's Windows CI
infrastructure. Reducing the test repetitions from 50 to 20 trims that
to about 20 seconds. Tests will timeout at 60 seconds, so this helps
keep the test reliable. (There was a timeout on CI today when testing an
unrelated code change.)

Refs: #7827 (comment)

The test takes 50 seconds on some of the project's Windows CI
infrastructure. Reducing the test repetitions from 50 to 20 trims that
to about 20 seconds. Tests will timeout at 60 seconds, so this helps
keep the test reliable. (There was a timeout on CI today when testing an
unrelated code change.)

Refs: nodejs#7827 (comment)
@Trott Trott added net Issues and PRs related to the net subsystem. windows Issues and PRs related to the Windows platform. test Issues and PRs related to the tests. labels Jul 27, 2016
@Trott
Copy link
Member Author

Trott commented Jul 27, 2016

@nodejs/testing

@Trott
Copy link
Member Author

Trott commented Jul 27, 2016

This version of the test taking 20 seconds per run: https://ci.nodejs.org/job/node-stress-single-test/835/nodes=win2008r2/console

Version on master taking 50 seconds per run: https://ci.nodejs.org/job/node-stress-single-test/832/nodes=win2008r2/console

@santigimeno
Copy link
Member

LGTM

2 similar comments
@JungMinu
Copy link
Member

LGTM

@targos
Copy link
Member

targos commented Jul 27, 2016

LGTM

@Trott
Copy link
Member Author

Trott commented Jul 27, 2016

@Trott
Copy link
Member Author

Trott commented Jul 29, 2016

CI failure looks infrastructure/build related and not anything to do with this change, but let's try again anyway: https://ci.nodejs.org/job/node-test-pull-request/3451/

@Trott
Copy link
Member Author

Trott commented Jul 29, 2016

CI is green. Landing...

Trott added a commit to Trott/io.js that referenced this pull request Jul 29, 2016
The test takes 50 seconds on some of the project's Windows CI
infrastructure. Reducing the test repetitions from 50 to 20 trims that
to about 20 seconds. Tests will timeout at 60 seconds, so this helps
keep the test reliable. (There was a timeout on CI today when testing an
unrelated code change.)

Refs: nodejs#7827 (comment)
PR-URL: nodejs#7886
Reviewed-By: Santiago Gimeno <[email protected]>
Reviewed-By: JungMinu - Minwoo Jung <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
@Trott
Copy link
Member Author

Trott commented Jul 29, 2016

Landed in 8fbdfb9

@Trott Trott closed this Jul 29, 2016
@cjihrig cjihrig mentioned this pull request Aug 8, 2016
cjihrig pushed a commit that referenced this pull request Aug 10, 2016
The test takes 50 seconds on some of the project's Windows CI
infrastructure. Reducing the test repetitions from 50 to 20 trims that
to about 20 seconds. Tests will timeout at 60 seconds, so this helps
keep the test reliable. (There was a timeout on CI today when testing an
unrelated code change.)

Refs: #7827 (comment)
PR-URL: #7886
Reviewed-By: Santiago Gimeno <[email protected]>
Reviewed-By: JungMinu - Minwoo Jung <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
@cjihrig cjihrig mentioned this pull request Aug 11, 2016
MylesBorins pushed a commit that referenced this pull request Oct 10, 2016
The test takes 50 seconds on some of the project's Windows CI
infrastructure. Reducing the test repetitions from 50 to 20 trims that
to about 20 seconds. Tests will timeout at 60 seconds, so this helps
keep the test reliable. (There was a timeout on CI today when testing an
unrelated code change.)

Refs: #7827 (comment)
PR-URL: #7886
Reviewed-By: Santiago Gimeno <[email protected]>
Reviewed-By: JungMinu - Minwoo Jung <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
rvagg pushed a commit that referenced this pull request Oct 18, 2016
The test takes 50 seconds on some of the project's Windows CI
infrastructure. Reducing the test repetitions from 50 to 20 trims that
to about 20 seconds. Tests will timeout at 60 seconds, so this helps
keep the test reliable. (There was a timeout on CI today when testing an
unrelated code change.)

Refs: #7827 (comment)
PR-URL: #7886
Reviewed-By: Santiago Gimeno <[email protected]>
Reviewed-By: JungMinu - Minwoo Jung <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
MylesBorins pushed a commit that referenced this pull request Oct 26, 2016
The test takes 50 seconds on some of the project's Windows CI
infrastructure. Reducing the test repetitions from 50 to 20 trims that
to about 20 seconds. Tests will timeout at 60 seconds, so this helps
keep the test reliable. (There was a timeout on CI today when testing an
unrelated code change.)

Refs: #7827 (comment)
PR-URL: #7886
Reviewed-By: Santiago Gimeno <[email protected]>
Reviewed-By: JungMinu - Minwoo Jung <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
@MylesBorins MylesBorins mentioned this pull request Oct 26, 2016
@Trott Trott deleted the faster branch January 13, 2022 22:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
net Issues and PRs related to the net subsystem. test Issues and PRs related to the tests. windows Issues and PRs related to the Windows platform.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants