| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
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.
Slightly confusing way to write this - but still LGTM.
Sorry, something went wrong.
|
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. |
Sorry, something went wrong.
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.
As of recently, this can just be:
assert.fail('Test failed: cluster worker is at a breakpoint.');
Sorry, something went wrong.
|
Are the requested changes OK? |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM if the CI is good. However, because this test uses common.PORT, it should probably be moved from parallel to sequential.
Sorry, something went wrong.
|
Can this proceed or does the test need to be moved from parallel to sequential? |
Sorry, something went wrong.
|
I would move it to sequential as long as common.PORT is there. |
Sorry, something went wrong.
because this test uses common.PORT, moved from parallel to sequential.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Ensure that cluster interoperates with the --inspect-brk option.
This does not test for —debug-brk.
Fixes: #11420
Checklist
Affected core subsystem(s)
test cluster