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: fix test-sync-io-option #1734

Closed
wants to merge 1 commit into from
Closed

test: fix test-sync-io-option #1734

wants to merge 1 commit into from

Conversation

santigimeno
Copy link
Member

  • Wait for all the data to be available in stderr before checking its contents.
    In FreeBSD this was failing because stderr data was being emitted in multiple chunks.
  • 4 WARNINGS are printed instead of 2 for each sync call inside readFileSync.
    require('fs') does not print any trace.

- Wait for all the data to be available in stderr before checking its contents.
  In FreeBSD this was failing because stderr data was being emitted in multiple chunks.
- 4 WARNINGS are printed instead of 2 for each sync call inside readFileSync.
  require('fs') does not print any trace.
@santigimeno
Copy link
Member Author

This test was failing in FreeBSD:

./out/Release/iojs test/parallel/test-sync-io-option.js 

assert.js:88
  throw new assert.AssertionError({
        ^
AssertionError: 0 == 2
    at ChildProcess.<anonymous> (/usr/home/sgimeno/node/io.js/test/parallel/test-sync-io-option.js:33:16)
    at emitTwo (events.js:87:13)
    at ChildProcess.emit (events.js:172:7)
    at Process.ChildProcess._handle.onexit (child_process.js:1009:12)

@silverwind silverwind added the test Issues and PRs related to the tests. label May 19, 2015
@Fishrock123
Copy link
Contributor

R=@trevnorris?

@Fishrock123
Copy link
Contributor

CI: https://jenkins-iojs.nodesource.com/view/iojs/job/iojs+any-pr+multi/690/

Centos5-32 is jenkins failing to connect to github for who knows why.

@trevnorris
Copy link
Contributor

Gah! What an idiotic oversight on my part. Thanks for getting the fix so promptly. LGTM.

@brendanashworth
Copy link
Contributor

This also just popped up in one of my OSX runs.

@brendanashworth brendanashworth self-assigned this May 20, 2015
brendanashworth pushed a commit that referenced this pull request May 20, 2015
Wait for all the data to be available in stderr before checking its
contents. In FreeBSD this was failing because stderr data was being
emitted in multiple chunks. 4 WARNINGS are printed instead of 2 for
each sync call inside readFileSync. require('fs') does not print any
trace.

PR-URL: #1734
Reviewed-By: Trevor Norris <[email protected]>
@brendanashworth
Copy link
Contributor

Thanks for the pull request! It has been landed in 8676319.

@brendanashworth brendanashworth removed their assignment May 20, 2015
@santigimeno santigimeno deleted the fix_sync_io_test branch May 20, 2015 09:11
@rvagg rvagg mentioned this pull request May 23, 2015
andrewdeandrade pushed a commit to andrewdeandrade/node that referenced this pull request Jun 3, 2015
Wait for all the data to be available in stderr before checking its
contents. In FreeBSD this was failing because stderr data was being
emitted in multiple chunks. 4 WARNINGS are printed instead of 2 for
each sync call inside readFileSync. require('fs') does not print any
trace.

PR-URL: nodejs/node#1734
Reviewed-By: Trevor Norris <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test Issues and PRs related to the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants