test: move test-debugger-address to parallel - #39236
Conversation
Sorry, something went wrong.
Sorry, something went wrong.
The test uses `--inspect=0` so it uses an OS-selected port rather than the default port. This means it can be run in the parallel directory. PR-URL: nodejs#39236 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
The test uses `--inspect=0` so it uses an OS-selected port rather than the default port. This means it can be run in the parallel directory. PR-URL: #39236 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
The test uses `--inspect=0` so it uses an OS-selected port rather than the default port. This means it can be run in the parallel directory. PR-URL: #39236 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
|
When using --inspect=0, is it possible to recover the port in use? If running a fork, how would that work? var worker = cp.fork('./my-script', {execArgv: ["--inspect=0"]}); Under what mechanism can the port used by the inspector be recovered? |
Sorry, something went wrong.
I believe you'd need to set stdio to 'pipe' so that you can get at the output from the fork command. The output will contain the web socket URL, including the port. |
Sorry, something went wrong.
The test uses --inspect=0 so it uses an OS-selected port rather than
the default port. This means it can be run in the parallel directory.