-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
clarify assertion failure #15889
clarify assertion failure #15889
Conversation
Hi, @ryshep111! Welcome and thanks for this! This change will cause the linter to fail. Try |
@@ -33,7 +33,7 @@ const fixtures = require('../common/fixtures'); | |||
assert.strictEqual( | |||
typeof global.gc, | |||
'function', | |||
'Run this test with --expose-gc' | |||
`Type of global.gc is not a function. Type: ${typeof global.gc}. Run this test with --expose-gc` |
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.
I will fix this while landing.
PR-URL: #15889 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Landed in 92d3269 Thanks for the PR, and congratulations on becoming a Node.js Contributor 🎉 ! |
PR-URL: #15889 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
PR-URL: nodejs/node#15889 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
assertion failure messages should always give the actual and expected results.