-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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: add inspect-brk option to cluster module #12503
Conversation
Ensure that cluster interoperates with the --inspect-brk option. This does not test for —debug-brk. Fixes: nodejs#11420
There was a problem hiding this comment.
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.
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. |
Have the cluster worker print something or crash. Then, test that it doesn't happen because the worker is at a breakpoint.
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.', '>'); |
There was a problem hiding this comment.
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.');
Are the requested changes OK? |
There was a problem hiding this comment.
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.
Can this proceed or does the test need to be moved from parallel to sequential? |
I would move it to sequential as long as |
because this test uses common.PORT, moved from parallel to sequential.
Landed in 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 <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
Should land with #12615 if that lands |
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 <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
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 <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
Ensure that cluster interoperates with the --inspect-brk option.
This does not test for —debug-brk.
Fixes: #11420
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
test cluster