Skip to content
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

Closed
wants to merge 1 commit into from

Conversation

maasencioh
Copy link
Contributor

Continues with the job proposed by @jasnell (there's still 217 occurrences in test/parallel)

Refs: #14332

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • commit message follows commit guidelines
Affected core subsystem(s)

test

@nodejs-github-bot nodejs-github-bot added async_hooks Issues and PRs related to the async hooks subsystem. doc Issues and PRs related to the documentations. dont-land-on-v4.x inspector Issues and PRs related to the V8 inspector protocol test Issues and PRs related to the tests. tools Issues and PRs related to the tools directory. labels Aug 9, 2017
@@ -1,13 +1,11 @@
/* eslint-disable required-modules */
Copy link
Contributor Author

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

Copy link
Member

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').

Copy link
Member

@jasnell jasnell left a 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

Trott
Trott previously requested changes Aug 10, 2017
Copy link
Member

@Trott Trott left a 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...

@targos
Copy link
Member

targos commented Aug 10, 2017

@Trott this is also true for fs.readFileSync(). No encoding was passed before so the behavior should be the same.

@Trott
Copy link
Member

Trott commented Aug 10, 2017

@Trott this is also true for fs.readFileSync(). No encoding was passed before so the behavior should be the same.

@targos You're right, of course. Never mind me.

@Trott Trott dismissed their stale review August 10, 2017 21:32

Comments were wrong. Dismissing.

@maasencioh maasencioh force-pushed the fixtures branch 2 times, most recently from db04014 to 80c5d6a Compare August 11, 2017 09:11
@maasencioh
Copy link
Contributor Author

I solved the conflicts with master and after that I have this error:

=== release test-require-symlink ===                                           
Path: parallel/test-require-symlink
assert.js:42
  throw new errors.AssertionError({
  ^

AssertionError [ERR_ASSERTION]: 1 === 0
    at ChildProcess.<anonymous> (/home/miguel/github/node/test/parallel/test-require-symlink.js:58:12)
    at emitTwo (events.js:125:13)
    at ChildProcess.emit (events.js:213:7)
    at maybeClose (internal/child_process.js:935:16)
    at Socket.stream.socket.on (internal/child_process.js:355:11)
    at emitOne (events.js:115:13)
    at Socket.emit (events.js:210:7)
    at Pipe._handle.close [as _onclose] (net.js:547:12)
Command: out/Release/node --preserve-symlinks /home/miguel/github/node/test/parallel/test-require-symlink.js
[02:02|% 100|+ 1758|-   1]: Done                                               
make: *** [Makefile:199: test] Error 1

Any idea why if I don't modify this file I got an error there?

@jasnell
Copy link
Member

jasnell commented Aug 23, 2017

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.

@maasencioh
Copy link
Contributor Author

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?

@jasnell
Copy link
Member

jasnell commented Aug 24, 2017

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!

@maasencioh
Copy link
Contributor Author

it's a great pleasure, I didn't have time to touch all the ones in parallel, but it's on my bucket list!

Copy link
Member

@tniessen tniessen left a 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.

CI: https://ci.nodejs.org/job/node-test-pull-request/9852/

@BridgeAR
Copy link
Member

Landed in 9a5c3cf

@BridgeAR BridgeAR closed this Aug 28, 2017
BridgeAR pushed a commit that referenced this pull request Aug 28, 2017
PR-URL: #14716
Refs: #14332
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Yuta Hiroto <[email protected]>
@maasencioh maasencioh deleted the fixtures branch August 28, 2017 08:04
@maasencioh
Copy link
Contributor Author

sorry to @tniessen , I didn't knew it but I'll have it in mind for next pr, thank you!

ghost pushed a commit to ayojs/ayo that referenced this pull request Aug 30, 2017
PR-URL: nodejs/node#14716
Refs: nodejs/node#14332
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Yuta Hiroto <[email protected]>
ghost pushed a commit to ayojs/ayo that referenced this pull request Aug 30, 2017
PR-URL: nodejs/node#14716
Refs: nodejs/node#14332
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Yuta Hiroto <[email protected]>
MylesBorins pushed a commit that referenced this pull request Sep 10, 2017
PR-URL: #14716
Refs: #14332
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Yuta Hiroto <[email protected]>
@MylesBorins MylesBorins mentioned this pull request Sep 10, 2017
MylesBorins pushed a commit that referenced this pull request Sep 11, 2017
PR-URL: #14716
Refs: #14332
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Yuta Hiroto <[email protected]>
MylesBorins pushed a commit that referenced this pull request Sep 12, 2017
PR-URL: #14716
Refs: #14332
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Yuta Hiroto <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
async_hooks Issues and PRs related to the async hooks subsystem. doc Issues and PRs related to the documentations. inspector Issues and PRs related to the V8 inspector protocol test Issues and PRs related to the tests. tools Issues and PRs related to the tools directory.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants