-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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: continue normalizing fixtures use #14716
Conversation
@@ -1,13 +1,11 @@ | |||
/* eslint-disable required-modules */ |
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.
I had to add this because the common package is not used after this change and therefore it conflicted withno-unused-vars
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.
You can just use require('../common')
.
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 with green CI
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.
Pretty sure an encoding needs to be sent to readKey()
if you want a string rather than a buffer. Probably best to keep the tests behavior the same, so we probably want to do that...
@Trott this is also true for |
db04014
to
80c5d6a
Compare
I solved the conflicts with master and after that I have this error:
Any idea why if I don't modify this file I got an error there? |
It's because you modified this file: test/fixtures/module-require-symlink/symlinked.js Generally, I would not change any of the files in the actual fixtures directory. |
indeed @jasnell , I had a typo in there, now all the test are passing, but I don't know if you want me to revert the ones in fixtures then? |
So long as all of the tests are passing, then it should be fine with the fixtures files edits. Those just tend to be very touchy with a number of the tests so it's best to be cautious. We'll get a good CI run and see where we're at. I really appreciate you doing this btw! |
it's a great pleasure, I didn't have time to touch all the ones in parallel, but it's on my bucket list! |
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.
I know we are not too strict about this in other test files, but if you get to test/parallel
, remember to keep the imports in ASCII order.
Landed in 9a5c3cf |
sorry to @tniessen , I didn't knew it but I'll have it in mind for next pr, thank you! |
PR-URL: nodejs/node#14716 Refs: nodejs/node#14332 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Yuta Hiroto <hello@about-hiroppy.com>
PR-URL: nodejs/node#14716 Refs: nodejs/node#14332 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Yuta Hiroto <hello@about-hiroppy.com>
Continues with the job proposed by @jasnell (there's still 217 occurrences in
test/parallel
)Refs: #14332
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
test