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-cluster-disconnect-handles hanging in background on freebsd #6988

Closed
rvagg opened this issue May 26, 2016 · 7 comments
Closed

test-cluster-disconnect-handles hanging in background on freebsd #6988

rvagg opened this issue May 26, 2016 · 7 comments
Labels
cluster Issues and PRs related to the cluster subsystem. test Issues and PRs related to the tests.

Comments

@rvagg
Copy link
Member

rvagg commented May 26, 2016

found 10 instances of this running on one of the freebsd CI machines, e.g:

iojs          97199   0.0  0.1 620772  1772  -  I    Sat09PM      0:00.09 /usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd10-64/out/Release/node --debug=12346. /usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd10-64/test/parallel/test-cluster-disconnect-handles.js
@rvagg
Copy link
Member Author

rvagg commented May 26, 2016

@nodejs/testing

@Trott Trott added test Issues and PRs related to the tests. cluster Issues and PRs related to the cluster subsystem. labels May 26, 2016
@Trott
Copy link
Member

Trott commented May 26, 2016

If nothing is jumping out at anyone in the code, maybe try running this test 10K times on freebsd in the stress test job and see if it fails at some point (and see if that failure causes subsequent runs to fail too). And, of course, fix whatever is causing the first failure.

I guess in the time it took me to type that out, I could have just kicked off the job. So here it is: https://ci.nodejs.org/job/node-stress-single-test/744/nodes=freebsd102-64/console

@cjihrig
Copy link
Contributor

cjihrig commented May 26, 2016

The stress test came back green. Are there any processes left behind?

@Trott
Copy link
Member

Trott commented May 26, 2016

Expanding scope a bit, judging from failures like https://ci.nodejs.org/job/node-test-commit-arm/3454/nodes=armv7-ubuntu1404/consoleFull it seems that some test somewhere is not cleaning up after itself reliably, even when it succeeds. I imagine it would manifest as a stray node process running and keeping the port open, resulting in the plethora of EADDRINUSE errors. I imagine this is a likely source of this issue. Not sure of an easy way to identify the problematic test, though. EDIT: Oh, actually, maybe this is the culprit test...

cjihrig added a commit to cjihrig/node that referenced this issue May 27, 2016
test-cluster-disconnect-handles already includes logic that
tries to cleanup any child processes when the test fails. This
commit adds additional checks to verify that the child exited
normally, and fails the test if that is not the case.

Refs: nodejs#6988
PR-URL: nodejs#6993
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Santiago Gimeno <[email protected]>
Fishrock123 pushed a commit to Fishrock123/node that referenced this issue May 30, 2016
test-cluster-disconnect-handles already includes logic that
tries to cleanup any child processes when the test fails. This
commit adds additional checks to verify that the child exited
normally, and fails the test if that is not the case.

Refs: nodejs#6988
PR-URL: nodejs#6993
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Santiago Gimeno <[email protected]>
@cjihrig
Copy link
Contributor

cjihrig commented Jun 1, 2016

@Trott, @rvagg can this one be closed? The issues with the CI from last week seem to be cleared up.

@Trott
Copy link
Member

Trott commented Jun 1, 2016

I think it can be closed.

@cjihrig
Copy link
Contributor

cjihrig commented Jun 1, 2016

OK. Closing. Please reopen if you think it needs to be investigated further.

@cjihrig cjihrig closed this as completed Jun 1, 2016
rvagg pushed a commit that referenced this issue Jun 2, 2016
test-cluster-disconnect-handles already includes logic that
tries to cleanup any child processes when the test fails. This
commit adds additional checks to verify that the child exited
normally, and fails the test if that is not the case.

Refs: #6988
PR-URL: #6993
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Santiago Gimeno <[email protected]>
MylesBorins pushed a commit that referenced this issue Jul 11, 2016
test-cluster-disconnect-handles already includes logic that
tries to cleanup any child processes when the test fails. This
commit adds additional checks to verify that the child exited
normally, and fails the test if that is not the case.

Refs: #6988
PR-URL: #6993
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Santiago Gimeno <[email protected]>
MylesBorins pushed a commit that referenced this issue Jul 12, 2016
test-cluster-disconnect-handles already includes logic that
tries to cleanup any child processes when the test fails. This
commit adds additional checks to verify that the child exited
normally, and fails the test if that is not the case.

Refs: #6988
PR-URL: #6993
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Santiago Gimeno <[email protected]>
MylesBorins pushed a commit that referenced this issue Jul 12, 2016
test-cluster-disconnect-handles already includes logic that
tries to cleanup any child processes when the test fails. This
commit adds additional checks to verify that the child exited
normally, and fails the test if that is not the case.

Refs: #6988
PR-URL: #6993
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Santiago Gimeno <[email protected]>
MylesBorins pushed a commit that referenced this issue Jul 14, 2016
test-cluster-disconnect-handles already includes logic that
tries to cleanup any child processes when the test fails. This
commit adds additional checks to verify that the child exited
normally, and fails the test if that is not the case.

Refs: #6988
PR-URL: #6993
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Santiago Gimeno <[email protected]>
MylesBorins pushed a commit that referenced this issue Jul 14, 2016
test-cluster-disconnect-handles already includes logic that
tries to cleanup any child processes when the test fails. This
commit adds additional checks to verify that the child exited
normally, and fails the test if that is not the case.

Refs: #6988
PR-URL: #6993
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Santiago Gimeno <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cluster Issues and PRs related to the cluster subsystem. test Issues and PRs related to the tests.
Projects
None yet
Development

No branches or pull requests

3 participants