-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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: fix test-child-process-stdin.js #10022
Conversation
37:5 error please use assert.strictEqual() instead of assert.equal() 39:5 error please use assert.strictEqual() instead of assert.equal()
@@ -34,8 +34,8 @@ cat.on('exit', common.mustCall(function(status) { | |||
|
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.
There are two uses of assert.ok()
in this file that could be greatly improved by changing to assert.strictEqual()
.
Ping @sriluvan: Can you update this per the comment from @cjihrig? The values passed to |
Hi. I will get it in by tomorrow. Sorry for the delay again. Thanks. |
I have fixed the issue and created the pull request. Again I'm sorry as I couldn't attend the request in time. This is first time I'm getting change in outside the group work held in Austin. I'm hoping I followed the guidelines properly. Please let know if any thing not done correctly. I'm hoping this delay won't repeat. Thanks. |
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.
Commit message is
37:5 error please use assert.strictEqual() instead of assert.equal()
39:5 error please use assert.strictEqual() instead of assert.equal()
That isn't useful, please put in a human readable description.
Use assert.strictEqual() instead of assert.equal().
Would be good.
The message I added was "assert.ok to assert.strictEqual" - as per the change requested in this thread. - not the message in your email. I opened the commit message in amend node to check what is the comments area but I don't see the message in your comment. Can you direct me. Thanks. |
The pull request with the suggested changes are in now. I'm not sure if this updated the original pull request or created new. Let me know if it is not update to original PR. Just want to know if I did the right steps. |
Closing in favor of #10420 |
Checklist
make -j8 test
(UNIX), orvcbuild test nosign
(Windows) passesAffected core subsystem(s)
test
Description of change
37:5 error please use assert.strictEqual() instead of assert.equal()
39:5 error please use assert.strictEqual() instead of assert.equal()