You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
parallel/test-repl-pretty-stack & parallel/test-repl-pretty-custom-stack assert the exact error message coming from V8 #43676
I'm enhancing the "Unexpected identifier" error message here https://chromium-review.googlesource.com/c/v8/v8/+/3726147 ; these tests would need to be updated once that change rolls into Node, or already in preparation for the change (by relaxing the assertion so that it passes both before and after the change).
Unfortunately, tests which assert the exact error message make improving the error messages more cumbersome than it has to be. :/ I don't have a good solution there; in this particular case it would've helped if the test asserted that there's "Unexpected identifier" somewhere in the error message (but allows more content than that).
How often does it reproduce? Is there a required condition?
Activity
BridgeAR commentedon Jul 4, 2022
@marjakh it should be fine to update the tests to only match for the
Unexpected identifier:targos commentedon Jul 18, 2022
@BridgeAR would you like to prepare a PR? Otherwise I can start from the diff you posted and do it. There's an example of the test failures with the new V8 in https://ci.nodejs.org/job/node-test-commit-linuxone/33075/
targos commentedon Jul 25, 2022
Fixed on
canary-base. Thanks for reporting!BridgeAR commentedon Jul 25, 2022
@targos thanks for doing that! I missed your comment before.