-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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: make debugging of inspector-port-zero easier #16685
Conversation
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 you address the comment.
proc.on('exit', mustCall((exitCode, signal) => assert.strictEqual( | ||
0, | ||
exitCode, | ||
`exitCode was ${exitCode} not 0, signal was ${signal}`))); |
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.
"not 0" is tautological here.
As well, the order of arguments is actual, expected[, message]
. You flipped them around here.
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.
"not 0" is tautological here.
True, just trying to save someone the trouble of having to look at the source. But thinking again, I think shorter is better.
As well, the order of arguments is actual, expected[, message]. You flipped them around here.
Huh, I always thought it was expected, actual
, guess I have to relearn that.
Both fixed.
65524b9
to
60a09fb
Compare
60a09fb
to
4f9fed6
Compare
4f9fed6
to
3feb60b
Compare
If the process was killed, then the exit code will be null, in which case knowing the signal is really helpful. PR-URL: nodejs#16685 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Eugene Ostroukhov <eostroukhov@google.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
3feb60b
to
5c7b1ec
Compare
If the process was killed, then the exit code will be null, in which case knowing the signal is really helpful. PR-URL: #16685 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Eugene Ostroukhov <eostroukhov@google.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
If the process was killed, then the exit code will be null, in which case knowing the signal is really helpful. PR-URL: #16685 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Eugene Ostroukhov <eostroukhov@google.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
If the process was killed, then the exit code will be null, in which case knowing the signal is really helpful. PR-URL: #16685 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Eugene Ostroukhov <eostroukhov@google.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
If the process was killed, then the exit code will be null, in which
case knowing the signal is really helpful.
Adding this because it failed for me with
exitCode
null, which isn't very helpful.Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
test