Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 34.2k
test: change assert.equal to assert.strictEqual#9956
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
Uh oh!
There was an error while loading. Please reload this page.
Conversation
crokita commented Dec 1, 2016 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
mscdex commented Dec 1, 2016
First line of commit message is too long, see the commit message guidelines here. |
jasnell left a comment
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. The commits will need to be squashed and a new-line needs to be added at the end of the file to pass linting.
Trott commented Dec 8, 2016
Trott commented Dec 22, 2016
ping @crokita: Can you add a newline to the end of the file? Even better if you can squash the commits into a single commit, but that can also be done by whoever lands the change. |
bde2cce to 30d5451Comparecrokita commented Dec 22, 2016
Yep! Updated the branch. Does this look okay @Trott ? |
Trott left a comment
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 CI is ✅
Trott commented Dec 22, 2016
italoacasas commented Dec 23, 2016
Landed 70d752e |
- Using assert.strictEqual instead assert.equal PR-URL: #9956 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Italo A. Casas <[email protected]>
Trott commented Dec 23, 2016
Thanks for the contribution @crokita! 🎉 |
- Using assert.strictEqual instead assert.equal PR-URL: #9956 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Italo A. Casas <[email protected]>
- Using assert.strictEqual instead assert.equal PR-URL: #9956 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Italo A. Casas <[email protected]>
- Using assert.strictEqual instead assert.equal PR-URL: #9956 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Italo A. Casas <[email protected]>
- Using assert.strictEqual instead assert.equal PR-URL: #9956 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Italo A. Casas <[email protected]>
- Using assert.strictEqual instead assert.equal PR-URL: #9956 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Italo A. Casas <[email protected]>
- Using assert.strictEqual instead assert.equal PR-URL: #9956 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Italo A. Casas <[email protected]>
- Using assert.strictEqual instead assert.equal PR-URL: #9956 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Italo A. Casas <[email protected]>
Checklist
make -j8 test(UNIX)Affected core subsystem(s)
test
Description of change
Use assert.strictEqual() instead of assert.equal() for lines 11, 12, 13, 14, 21, 22, 23, 24, 28