Skip to content

test: add inspect-brk option to cluster module - #12503

Closed
dave-k wants to merge 4 commits into
nodejs:masterfrom
dave-k:1140_test_cluster_inspect-brk
Closed

test: add inspect-brk option to cluster module#12503
dave-k wants to merge 4 commits into
nodejs:masterfrom
dave-k:1140_test_cluster_inspect-brk

Conversation

@dave-k

@dave-kdave-k commented Apr 19, 2017

Copy link
Copy Markdown
Contributor

Ensure that cluster interoperates with the --inspect-brk option.
This does not test for —debug-brk.

Fixes: #11420

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

test cluster

@dave-k
test: add inspect-brk option to cluster module
7260dd5
Ensure that cluster interoperates with the --inspect-brk option.
This does not test for —debug-brk.
Fixes: nodejs#11420
@nodejs-github-botnodejs-github-bot added the test Issues and PRs related to the tests. label Apr 19, 2017
@hiroppyhiroppy added the cluster Issues and PRs related to the cluster subsystem. label Apr 19, 2017
benjamingr
benjamingr approved these changes Apr 19, 2017
View reviewed changes

@benjamingrbenjamingr left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Slightly confusing way to write this - but still LGTM.

@cjihrig

cjihrig commented Apr 19, 2017

Copy link
Copy Markdown
Contributor

It might be helpful to have the cluster worker print something or crash. Then, you can test that it doesn't happen because the worker is at a breakpoint.

@dave-k
test: assert fail if breakpoint not reached
61d06c5
Have the cluster worker print something or crash.
Then, test that it doesn't happen
because the worker is at a breakpoint.
cjihrig
cjihrig requested changes Apr 19, 2017
View reviewed changes
Comment threadtest/parallel/test-cluster-inspect-brk.js Outdated
test([`--inspect-brk=${debuggerPort}`]);
} else {
// Cluster worker is at a breakpoint, should not reach here.
assert.fail(1, 2, 'Test failed: cluster worker is at a breakpoint.', '>');

@cjihrigcjihrigApr 19, 2017

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

As of recently, this can just be:

assert.fail('Test failed: cluster worker is at a breakpoint.');

@dave-k

dave-k commented Apr 20, 2017

Copy link
Copy Markdown
ContributorAuthor

Are the requested changes OK?

cjihrig
cjihrig approved these changes Apr 20, 2017
View reviewed changes

@cjihrigcjihrig left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM if the CI is good. However, because this test uses common.PORT, it should probably be moved from parallel to sequential.

@dave-k

dave-k commented Apr 24, 2017

Copy link
Copy Markdown
ContributorAuthor

Can this proceed or does the test need to be moved from parallel to sequential?

@cjihrig

cjihrig commented Apr 25, 2017

Copy link
Copy Markdown
Contributor

I would move it to sequential as long as common.PORT is there.

@dave-k
test: move test from parallel to sequential
c8f4d11
because this test uses common.PORT, moved from parallel to sequential.
@cjihrig

cjihrig commented Apr 25, 2017

Copy link
Copy Markdown
Contributor

CI: https://ci.nodejs.org/job/node-test-pull-request/7672/

@addaleax

addaleax commented Apr 29, 2017

Copy link
Copy Markdown
Member

Landed in 0324ac6

addaleax pushed a commit that referenced this pull request Apr 29, 2017
@dave-k@addaleax
test: add inspect-brk option to cluster module
0324ac6
Ensure that cluster interoperates with the --inspect-brk option.
This does not test for --debug-brk.
Fixes: #11420
PR-URL: #12503
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@jasnelljasnell mentioned this pull request May 11, 2017
Closed
@gibfahngibfahn mentioned this pull request Jun 15, 2017
Closed
3 tasks
@gibfahn

gibfahn commented Jun 18, 2017

Copy link
Copy Markdown
Member

Should land with #12615 if that lands

@gibfahngibfahn mentioned this pull request Jun 18, 2017
Closed
3 tasks
MylesBorins pushed a commit that referenced this pull request Oct 16, 2017
@dave-k@MylesBorins
test: add inspect-brk option to cluster module
1de5797
Ensure that cluster interoperates with the --inspect-brk option.
This does not test for --debug-brk.
Fixes: #11420
PR-URL: #12503
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@MylesBorinsMylesBorins mentioned this pull request Oct 17, 2017
Merged
MylesBorins pushed a commit that referenced this pull request Oct 25, 2017
@dave-k@MylesBorins
test: add inspect-brk option to cluster module
7b9710d
Ensure that cluster interoperates with the --inspect-brk option.
This does not test for --debug-brk.
Fixes: #11420
PR-URL: #12503
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@MylesBorinsMylesBorins mentioned this pull request Nov 3, 2017
Merged
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@benjamingrbenjamingrbenjamingr approved these changes
@cjihrigcjihrigcjihrig approved these changes

Assignees

No one assigned

Labels

clusterIssues and PRs related to the cluster subsystem.testIssues and PRs related to the tests.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Implement a test to ensure that cluster properly interoperates with the --{inspect,debug}-brk options

8 participants

@dave-k@cjihrig@addaleax@gibfahn@benjamingr@MylesBorins@hiroppy@nodejs-github-bot