-
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: update test failure output to include exit code and signal #15945
Conversation
assert.strictEqual(code, 0, 'worker1 did not exit normally'); | ||
assert.strictEqual(signal, null, 'worker1 did not exit normally'); | ||
assert.strictEqual(code, 0, `worker1 did not exit normally. exited with code ${code}`); | ||
assert.strictEqual(signal, null, `worker1 did not exit normally. exited with signal ${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.
The line length exceeds 80 characters here. This has to be fixed but it can also be done while landing.
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.
done
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 but will definitely need line wrapping to pass linting.
d0d8c60
to
4fd69e2
Compare
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.
assert.strictEqual(code, 0, `worker2 did not exit normally. exited with\ | ||
code ${code}`); | ||
assert.strictEqual(signal, null, `worker2 did not exit normally. exited\ | ||
with signal ${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.
The basic change is good but we try to avoid using multi-line template literals in core. This can be improved by...
assert.strictEqual(code, 0,
'worker2 did not exit normally.' +
`exited with code ${code}`);
assert.strictEqual(signal, null,
'worker2 did not exit normally. ' +
`exited with signal ${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.
That can be fixed on landing tho :-)
PR-URL: #15945 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]
Landed in da7d92e. |
PR-URL: #15945 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]
PR-URL: nodejs/node#15945 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]
PR-URL: #15945 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]
PR-URL: #15945 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]
PR-URL: #15945 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)