-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Adding additional error details for asserts. #16116
Conversation
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.
Just fyi for next time... Opening a new pr is unnecessary but fine. New commits to existing prs can be added. Let one of us know if you need extra assistance figuring that out! Thank you for the contribution!
Thanks! Can you fix the commit message to adhere to our guidlines? (needs a double line break otherwise it runs on and on, also a subsystem prefix). Much appreciated 😄 |
test/parallel/test-vm-context.js
Outdated
}, 'Expected appearance of proper offset in Error stack'); | ||
assertErrStack = err.stack; | ||
return /expected-filename\.js:33:130/.test(err.stack); | ||
}, `expected appearance of proper offset in Error stack: ${assertErrStack}`); |
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.
This test lost two parts that were tested here before. Testing for ^
was definitely intended and should be further tested for. I am also relatively sure the space in front of the throw was intended as well to test for the correct column number.
It would probably be best to just remove the error message overall.
test/parallel/test-vm-context.js
Outdated
'expected exception from runInContext signature test'); | ||
let eMessage = 'expected exception from '; | ||
eMessage += `runInContext signature test: ${gh1140Exception}`; | ||
assert.ok(gh1140Exception, eMessage); |
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.
It would be nicer to just use string concatenation instead of adding a separated variable.
ping @burgerboydaddy |
Hello,
I'm sorry I was on vacation; can somebody tell me what is required for this
issue right now and if possible how to submit fix without new pull request.
thanks
…On Sat, Oct 21, 2017 at 10:51 PM, Gireesh Punathil ***@***.*** > wrote:
ping @burgerboydaddy <https://github.com/burgerboydaddy>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16116 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ADmwn09E4-8e8siqbYfH8_YE5XYtPMc-ks5sutfWgaJpZM4PzYWk>
.
|
The cleanup needed here was a little awkward to explain so I just went ahead and did it. Hope that's OK. This should be ready to go, I think . PTAL, especially those of you that approved a previous version. @jasnell @fhinkel @gireeshpunathil |
PR-URL: nodejs#16116 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Franziska Hinkelmann <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Joyee Cheung <[email protected]>
Landed in 5163757 |
PR-URL: #16116 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Franziska Hinkelmann <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Joyee Cheung <[email protected]>
PR-URL: #16116 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Franziska Hinkelmann <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Joyee Cheung <[email protected]>
PR-URL: #16116 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Franziska Hinkelmann <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Joyee Cheung <[email protected]>
PR-URL: nodejs/node#16116 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Franziska Hinkelmann <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Joyee Cheung <[email protected]>
PR-URL: nodejs/node#16116 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Franziska Hinkelmann <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Joyee Cheung <[email protected]>
PR-URL: #16116 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Franziska Hinkelmann <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Joyee Cheung <[email protected]>
PR-URL: #16116 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Franziska Hinkelmann <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Joyee Cheung <[email protected]>
PR-URL: #16116 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Franziska Hinkelmann <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Joyee Cheung <[email protected]>
PR-URL: nodejs/node#16116 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Franziska Hinkelmann <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Joyee Cheung <[email protected]>
Adding additional error details for asserts. Proper fix for pull request #16009
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
test