-
Notifications
You must be signed in to change notification settings - Fork 30k
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: better error message in trace events test #20655
test: better error message in trace events test #20655
Conversation
CI: https://ci.nodejs.org/job/node-test-commit/18378/ Please 👍 for fast-tracking. |
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 it might make sense to add a sentence that every id should be above 0, no?
@BridgeAR I think anybody who’s looking into a failure of this assertion would look at the test code anyway. But if you have some concrete suggestion, feel free to push directly to this PR. :) |
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. Super-micro-nit that you should totally ignore if you don't agree with it: Semantically, I prefer assert.ok()
in tests (and assert()
for stuff in production/lib
code). So maybe take this opportunity to fix up line 62?
54e3089
to
051ea50
Compare
@Trott Very much fine with that, done! :) |
@Trott would you be so kind and open a small poll to see how people would prefer this in general? If there is a specific preference we could just add a lint rule for it. Right now this is very mixed and it will stay that way as there are likely different preferences (if people have a preference or opinion at all). |
Landed in f8fc2f8 |
PR-URL: nodejs#20655 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
PR-URL: #20655 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes