-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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_runner: account for newline in source maps #54444
Conversation
Review requested:
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #54444 +/- ##
=======================================
Coverage 87.32% 87.32%
=======================================
Files 648 648
Lines 182359 182359
Branches 34981 34983 +2
=======================================
Hits 159239 159239
+ Misses 16386 16384 -2
- Partials 6734 6736 +2
|
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
FWIW @yume-chan appears to send their commits as |
This commit updates the source mapping logic in the test runner to account for newline characters that are not included in line length calculations. Co-authored-by: Simon Chan <1330321+yume-chan@users.noreply.github.com> Fixes: nodejs#54240
Thanks @RedYetiDev |
Landed in 821ffab |
This commit updates the source mapping logic in the test runner to account for newline characters that are not included in line length calculations. Co-authored-by: Simon Chan <1330321+yume-chan@users.noreply.github.com> Fixes: #54240 PR-URL: #54444 Reviewed-By: Jake Yuesong Li <jake.yuesong@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
This commit updates the source mapping logic in the test runner to account for newline characters that are not included in line length calculations.
Fixes: #54240
@yume-chan would you like to be included as a coauthor on this PR? I added the Co-authored-by metadata, but I don't know what email address you'd like to use in it.