Skip to content

Conversation

@Trott
Copy link
Member

test-domain-abort-on-uncaught is flaky under load. Move it to sequential
so it is not competing with other tests for resources.

Fixes: #11814

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

test domain

@TrottTrott added domain Issues and PRs related to the domain subsystem. test Issues and PRs related to the tests. labels Mar 12, 2017
test-domain-abort-on-uncaught is flaky under load. Move it to sequential so it is not competing with other tests for resources. Fixes: nodejs#11814
@TrottTrottforce-pushed the flaky-domain-test branch from 862b69e to 8af27d5CompareMarch 12, 2017 16:14
@TrottTrott changed the title test: move flaky test to sequentialtest: fix flaky test-domain-abort-on-uncaughtMar 12, 2017
@Trott
Copy link
MemberAuthor

@Trott
Copy link
MemberAuthor

@Trott
Copy link
MemberAuthor

Whoops, ran the initial stress test on the wrong architecture.

Stress test again on master (should show failures): https://ci.nodejs.org/job/node-stress-single-test/1122/nodes=armv7-ubuntu1404/console

Stress test on this PR (should succeed): https://ci.nodejs.org/job/node-stress-single-test/1123/nodes=armv7-ubuntu1404/console

@Trott
Copy link
MemberAuthor

Amping up the stress test a bit more to 16 parallel processes.

Master (should fail): https://ci.nodejs.org/job/node-stress-single-test/1127/nodes=armv7-ubuntu1404/console

This PR (should succeed): https://ci.nodejs.org/job/node-stress-single-test/1128/nodes=armv7-ubuntu1404/console

@Trott
Copy link
MemberAuthor

Amping up the stress test a bit more to 32 parallel processes.

Master (should fail): https://ci.nodejs.org/job/node-stress-single-test/1129/nodes=armv7-ubuntu1404/console

This PR (should succeed): https://ci.nodejs.org/job/node-stress-single-test/1130/nodes=armv7-ubuntu1404/console

@Trott
Copy link
MemberAuthor

(Current master is failing the stress test, this PR is passing it.)

@TrottTrott closed this Mar 13, 2017
@TrottTrott reopened this Mar 13, 2017
@jasnell
Copy link
Member

New CI since there was a failure on Windows: https://ci.nodejs.org/job/node-test-pull-request/6844/

jasnell pushed a commit that referenced this pull request Mar 16, 2017
test-domain-abort-on-uncaught is flaky under load. Move it to sequential so it is not competing with other tests for resources. PR-URL: #11817Fixes: #11814 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Daijiro Wachi <[email protected]> Reviewed-By: Santiago Gimeno <[email protected]> Reviewed-By: Yuta Hiroto <[email protected]> Reviewed-By: James M Snell <[email protected]>
@jasnell
Copy link
Member

Landed in 5e3d536

@jasnelljasnell closed this Mar 16, 2017
italoacasas pushed a commit to italoacasas/node that referenced this pull request Mar 20, 2017
test-domain-abort-on-uncaught is flaky under load. Move it to sequential so it is not competing with other tests for resources. PR-URL: nodejs#11817Fixes: nodejs#11814 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Daijiro Wachi <[email protected]> Reviewed-By: Santiago Gimeno <[email protected]> Reviewed-By: Yuta Hiroto <[email protected]> Reviewed-By: James M Snell <[email protected]>
@italoacasasitaloacasas mentioned this pull request Mar 20, 2017
jungx098 pushed a commit to jungx098/node that referenced this pull request Mar 21, 2017
test-domain-abort-on-uncaught is flaky under load. Move it to sequential so it is not competing with other tests for resources. PR-URL: nodejs#11817Fixes: nodejs#11814 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Daijiro Wachi <[email protected]> Reviewed-By: Santiago Gimeno <[email protected]> Reviewed-By: Yuta Hiroto <[email protected]> Reviewed-By: James M Snell <[email protected]>
MylesBorins pushed a commit that referenced this pull request Apr 18, 2017
test-domain-abort-on-uncaught is flaky under load. Move it to sequential so it is not competing with other tests for resources. PR-URL: #11817Fixes: #11814 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Daijiro Wachi <[email protected]> Reviewed-By: Santiago Gimeno <[email protected]> Reviewed-By: Yuta Hiroto <[email protected]> Reviewed-By: James M Snell <[email protected]>
MylesBorins pushed a commit that referenced this pull request Apr 19, 2017
test-domain-abort-on-uncaught is flaky under load. Move it to sequential so it is not competing with other tests for resources. PR-URL: #11817Fixes: #11814 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Daijiro Wachi <[email protected]> Reviewed-By: Santiago Gimeno <[email protected]> Reviewed-By: Yuta Hiroto <[email protected]> Reviewed-By: James M Snell <[email protected]>
@MylesBorinsMylesBorins mentioned this pull request Apr 19, 2017
andrew749 pushed a commit to michielbaird/node that referenced this pull request Jul 19, 2017
test-domain-abort-on-uncaught is flaky under load. Move it to sequential so it is not competing with other tests for resources. PR-URL: nodejs/node#11817Fixes: nodejs/node#11814 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Daijiro Wachi <[email protected]> Reviewed-By: Santiago Gimeno <[email protected]> Reviewed-By: Yuta Hiroto <[email protected]> Reviewed-By: James M Snell <[email protected]>
@TrottTrott deleted the flaky-domain-test branch January 13, 2022 22:45
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

domainIssues and PRs related to the domain subsystem.testIssues and PRs related to the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

investigate flaky test-domain-abort-on-uncaught

8 participants

@Trott@jasnell@santigimeno@watilde@cjihrig@hiroppy@gibfahn@MylesBorins