test-debug-port-cluster or test-debug-signal-cluster hanging in background on freebsd

[rvagg]

found ~550 (not a typo) instances of test/fixtures/clustered-server/app.js running on one of the freebsd CI machines, this is used by both test-debug-port-cluster and test-debug-signal-cluster and I'm not sure which one was parent. Typical entries look like:

iojs          11971   0.0  0.2  620776  3556  -  I    16May16      0:00.09 /usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd10-64/out/Release/node --debug=13683 /usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd10-64/test/fixtures/clustered-server/app.js

@nodejs/testing

[Trott]

Not sure I have a fully coherentl explanation as to how this could plausibly cause the issue but the +1000 in this line seems like a code smell to me. Ought to just be common.PORT. Will submit a PR momentarily...

[cjihrig]

Could we build something into the CI or test runner to 1) detect tests that leave orphans running. 2) log that information somewhere. 3) kill the orphans.

[Trott]

@cjihrig I imagine the main challenge would be distinguishing between orphans and other tests that are running in parallel.

[cjihrig]

From a little Googling, it seems like identifying orphans is possible. I just don't know that we could associate that back to individual tests.

[cjihrig]

@Trott can this be closed?

[Trott]

Yes. Closing.