Uh oh!
There was an error while loading. Please reload this page.
test: fix domain-top-level-error-handler-throw - #4364
Conversation
misterdjules
commented
Dec 22, 2015
I ran that test as: and I haven't been able to see it fail. Did you manage to reproduce the flakiness of this test? A minor nit to the commit message: the first line of the description is longer than 72 characters, but that can be changed when landing it, so no worries. Other than that, LGTM and we don't necessarily have to reproduce the flakiness to land this change, as it's definitely more correct to wait for Added lts-watch-* labels as this test is present in all LTS branches with the same issue. |
misterdjules
commented
Dec 23, 2015
Check the stderr output in the `close` event as it's not guaranteed to be fully available when the `exit` event is fired.
31db233 to
c52fdd9Comparesantigimeno
commented
Dec 23, 2015
@misterdjules I could reproduce in I've already fixed the description. Thanks! |
misterdjules
commented
Dec 23, 2015
@santigimeno I couldn't reproduce the problem on my OSX setup even when running multiple instances of Thank you! |
misterdjules
commented
Dec 23, 2015
Landed in cf50305. |
Trott
commented
Dec 24, 2015
It appears that the code in this PR is breaking CI. The specific test broken is in the addons. Here's an example from https://ci.nodejs.org/job/node-test-commit-osx/1553/nodes=osx1010/console: |
MylesBorins
commented
Dec 24, 2015
I'll have a PR in just a moment to revert this |
PR-URL: nodejs#4410 As @Trott points out in nodejs#4364 commit cf50305 is currently breaking CI. This commit reverts the changes.
MylesBorins
commented
Dec 24, 2015
I'm reopening this now that the new PR is in |
MylesBorins
commented
Dec 24, 2015
This does not appear to be breaking things |
Trott
commented
Dec 24, 2015
Apologies for the bad diagnosis! |
Check the stderr output in the `close` event as it's not guaranteed to be fully available when the `exit` event is fired. PR: nodejs#4364 PR-URL: nodejs#4364 Reviewed-By: Julien Gilli <jgilli@fastmail.fm>
Check the stderr output in the `close` event as it's not guaranteed to be fully available when the `exit` event is fired. PR: nodejs#4364 PR-URL: nodejs#4364 Reviewed-By: Julien Gilli <jgilli@fastmail.fm>
Check the stderr output in the
closeevent as it's not guaranteed to be fullyavailable when the
exitevent is fired.It tries to fix#4206.