Description
This seems to have started today and seems to be making it all but impossible to get a green CI on Raspberry Pi (arm-fanned).
Inspector tests are leaving around stale jobs. Here's a partial copy/paste of an exchange between @refack and me in the node-build IRC channel:
me:
Hanging process is:
home/iojs/build/workspace/node-test-binary-arm/out/Release/node --inspect=0 -p process.debugPort
I don't have access to test-requireio_kahwee-debian9-arm64_pi3-1 but it looks like it could use the same treatment. refack rvagg
Took that one offline. Guess it needs to be added to the ansible playbook for writing the ssh config file.
refack:
I saw
home/iojs/build/workspace/node-test-binary-arm/out/Release/node --inspect=0 -p process.debugPortonceejbot-debian9-armv6l_pi1p-1as well . Opening an issue
me:
Gotta be test/sequential/test-inspector-port-zero-cluster.js since that one fails so often. Probably leaves a process around when it fails.
Different one on test-requireio_mininodes-debian9-armv6l_pi1p-1 but still an inspector test.
/home/iojs/build/workspace/node-test-binary-arm/out/Release/node --inspect -e const assert = require('assert'); const inspector = process.binding('inspector'); assert( !!inspector.isEnabled(), 'inspector.isEnabled() should be true when run with --inspect'); process._debugEnd(); assert( !inspector.isEnabled(), 'inspector.isEnabled() should be false after _debugEnd()');
Not seeing the issue. Did you open it, refack? Maybe I'm looking in the wrong repo.
Meanwhile test-requireio_continuationlabs-debian9-armv6l_pi1p-1 has 18 of these running:/home/iojs/build/workspace/node-test-binary-arm/out/Release/node --inspect=12391 /home/iojs/build/workspace/node-test-binary-arm/test/sequential/test-inspector-port-cluster.jsSame forr test-requireio_mininodes-debian9-armv7l_pi2-1
(Although fewer there. Only 6.
@nodejs/v8-inspector @nodejs/build @nodejs/testing