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: move test-cluster-debug-port to sequential #16292

Closed
wants to merge 1 commit into from

Conversation

al-k21
Copy link

@al-k21 al-k21 commented Oct 18, 2017

This test cannot be run in parallel, as it can conflict with other tests using the debug port. I suggest making this test sequential.

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

test

This test cannot be run in parallel, as it can conflict with other tests
using the debug port.
@nodejs-github-bot nodejs-github-bot added test Issues and PRs related to the tests. v6.x labels Oct 18, 2017
@gibfahn
Copy link
Member

gibfahn commented Oct 18, 2017

Note that this test has already been removed from master.

cc/ @nodejs/testing

@mscdex mscdex added the cluster Issues and PRs related to the cluster subsystem. label Oct 19, 2017
MylesBorins pushed a commit that referenced this pull request Oct 19, 2017
This test cannot be run in parallel, as it can conflict with other tests
using the debug port.

PR-URL: #16292
Reviewed-By: Gibson Fahnestock <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
@MylesBorins
Copy link
Contributor

landed in f65f691

MylesBorins pushed a commit that referenced this pull request Oct 19, 2017
This test cannot be run in parallel, as it can conflict with other tests
using the debug port.

PR-URL: #16292
Reviewed-By: Gibson Fahnestock <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
@MylesBorins MylesBorins mentioned this pull request Oct 19, 2017
MylesBorins pushed a commit that referenced this pull request Oct 25, 2017
This test cannot be run in parallel, as it can conflict with other tests
using the debug port.

PR-URL: #16292
Reviewed-By: Gibson Fahnestock <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
MylesBorins pushed a commit that referenced this pull request Oct 25, 2017
This test cannot be run in parallel, as it can conflict with other tests
using the debug port.

PR-URL: #16292
Reviewed-By: Gibson Fahnestock <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
@MylesBorins MylesBorins mentioned this pull request Oct 25, 2017
MylesBorins pushed a commit that referenced this pull request Oct 26, 2017
This test cannot be run in parallel, as it can conflict with other tests
using the debug port.

PR-URL: #16292
Reviewed-By: Gibson Fahnestock <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cluster Issues and PRs related to the cluster subsystem. test Issues and PRs related to the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.