-
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
test: fix single test runner regression #15329
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 if CI is green. I'd be +1 on landing this sooner than the usual 48/72 hours.
ab2b409
to
434825d
Compare
test-pull-request: https://ci.nodejs.org/job/node-test-pull-request/10032/ stress-single-test with five different flavors of single tests (.js test with .js, .js test w/o .js, .mjs test with .mjs, .mjs test w/o .mjs, directory): https://ci.nodejs.org/job/node-stress-single-test/1408/nodes=ubuntu1610-x64/ |
Thanks for doing this. Wasn't familiar with this code, good to see there's a cleaner way. |
I think we should consider fast tracking this commit. If it lands before the EOD we can get it into the 8.5.0 release |
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
@TimothyGu's stress test seems to have worked (it ran all the tests) so I'd be good with landing this. Quick ping to @nodejs/python @nodejs/testing |
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 but the commit log should go into more detail.
The regression was introduced in #14369, right?
landed in cb44cd4 |
When ESM support was added it created a regression in the test runner that broke the ability to run individual tests. This commit re-introduces the use of `NormalizePath` which fixes the regression in the test runner Refs: #15300 PR-URL: #15329 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
When ESM support was added it created a regression in the test runner that broke the ability to run individual tests. This commit re-introduces the use of `NormalizePath` which fixes the regression in the test runner Refs: #15300 PR-URL: #15329 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
When ESM support was added it created a regression in the test runner that broke the ability to run individual tests. This commit re-introduces the use of `NormalizePath` which fixes the regression in the test runner Refs: nodejs#15300 PR-URL: nodejs#15329 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Alternative to #15300.
/cc @apapirovski
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
test
Refs: #15300.
Refs: #14369