Skip to content
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

Merged
merged 1 commit into from
Nov 20, 2017

Conversation

gibfahn
Copy link
Member

@gibfahn gibfahn commented Nov 2, 2017

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), or vcbuild test (Windows) passes
  • commit message follows commit guidelines
Affected core subsystem(s)

test

@nodejs-github-bot nodejs-github-bot added the test Issues and PRs related to the tests. label Nov 2, 2017
Copy link
Member

@bnoordhuis bnoordhuis left a 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}`)));
Copy link
Member

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.

Copy link
Member Author

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.

@mscdex mscdex added the inspector Issues and PRs related to the V8 inspector protocol label Nov 2, 2017
@joyeecheung
Copy link
Member

@gibfahn
Copy link
Member Author

gibfahn commented Nov 13, 2017

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>
@gibfahn gibfahn merged commit 5c7b1ec into nodejs:master Nov 20, 2017
@gibfahn gibfahn deleted the inspector-test branch November 20, 2017 15:04
MylesBorins pushed a commit that referenced this pull request Dec 12, 2017
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>
@MylesBorins MylesBorins mentioned this pull request Dec 12, 2017
gibfahn added a commit that referenced this pull request Dec 19, 2017
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>
@gibfahn gibfahn mentioned this pull request Dec 20, 2017
gibfahn added a commit that referenced this pull request Dec 20, 2017
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>
@gibfahn gibfahn mentioned this pull request Dec 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
inspector Issues and PRs related to the V8 inspector protocol test Issues and PRs related to the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.