Skip to content

Conversation

@santigimeno
Copy link
Member

Checklist
  • tests and code linting passes
  • the commit message follows commit guidelines
Affected core subsystem(s)

test

Description of change

Make sure that catch-stdout-error has written data before the
destination process exits.

Fixes: #6791

Stress test on FreeBSD without this change fails: https://ci.nodejs.org/job/node-stress-single-test/727/

Stress test with this change succeeds: https://ci.nodejs.org/job/node-stress-single-test/731/

@nodejs-github-botnodejs-github-bot added the test Issues and PRs related to the tests. label May 17, 2016
@mscdexmscdex added stream Issues and PRs related to the stream subsystem. process Issues and PRs related to the process subsystem. labels May 17, 2016
@cjihrig
Copy link
Contributor

LGTM

@santigimeno
Copy link
MemberAuthor

@jasnell
Copy link
Member

LGTM

1 similar comment
@r-52
Copy link
Contributor

r-52 commented May 17, 2016

LGTM

Make sure that `catch-stdout-error` has written data before the destination process exits. Fixes: nodejs#6791 PR-URL: nodejs#6808 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Roman Klauke <[email protected]>
@santigimeno
Copy link
MemberAuthor

CI is green. Landing now.

@santigimenosantigimeno merged commit 89460f1 into nodejs:masterMay 18, 2016
@santigimenosantigimeno deleted the close_catch branch May 18, 2016 08:22
@santigimeno
Copy link
MemberAuthor

Landed in 89460f1

@santigimeno
Copy link
MemberAuthor

Thanks

Fishrock123 pushed a commit that referenced this pull request May 23, 2016
Make sure that `catch-stdout-error` has written data before the destination process exits. Fixes: #6791 PR-URL: #6808 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Roman Klauke <[email protected]>
rvagg pushed a commit that referenced this pull request Jun 2, 2016
Make sure that `catch-stdout-error` has written data before the destination process exits. Fixes: #6791 PR-URL: #6808 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Roman Klauke <[email protected]>
MylesBorins pushed a commit that referenced this pull request Jun 3, 2016
Make sure that `catch-stdout-error` has written data before the destination process exits. Fixes: #6791 PR-URL: #6808 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Roman Klauke <[email protected]>
@MylesBorinsMylesBorins mentioned this pull request Jun 24, 2016
MylesBorins pushed a commit that referenced this pull request Jun 24, 2016
Make sure that `catch-stdout-error` has written data before the destination process exits. Fixes: #6791 PR-URL: #6808 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Roman Klauke <[email protected]>
MylesBorins pushed a commit that referenced this pull request Jun 24, 2016
Make sure that `catch-stdout-error` has written data before the destination process exits. Fixes: #6791 PR-URL: #6808 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Roman Klauke <[email protected]>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

processIssues and PRs related to the process subsystem.streamIssues and PRs related to the stream subsystem.testIssues and PRs related to the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

investigate flaky parallel/test-stdout-close-catch on FreeBSD

7 participants

@santigimeno@cjihrig@jasnell@r-52@mscdex@MylesBorins@nodejs-github-bot