test-debug-port-from-cmdline odd behaviour

[mathiask88]

I recently ran the parallel tests on my win8.1x64 machine and saw a strange behaviour of test-debug-port-from-cmdline. For the release build the test passed but for the debug build not. The startup time for a node process in debug build is ~2secs and the child process was closed before the parent had a chance to connect the debugger.
Is this normal that the release and debug builds show different behaviours?

Test gists:
https://gist.github.com/mathiask88/af67b5b7b60bab5ce990
https://gist.github.com/mathiask88/6e4763580649eb06fe2e

[silverwind]

Not normal. I think it's safe to assume that there is some underlying bug here which results in intermittent test failures. We thought they were related to our CI machines, but your experience shows it happens in the wild too.

See #2094 and #2149 for some (likely misguided) attempts at fixing it.

@orangemocha another new error on this test. It translate to 'The system cannot find the given file':

not ok 136 - test-debug-port-from-cmdline.js
#C:\Users\Mathias\Documents\GitHub\io.js\test\parallel\test-debug-port-from-cmdline.js:20
#    process._debugProcess(child.pid);
#            ^
#Error: Das System kann die angegebene Datei nicht finden.
#    at Error (native)
#    at ChildProcess.onChildMsg (C:\Users\Mathias\Documents\GitHub\io.js\test\parallel\test-debug-port-from-cmdline.js:20:13)
#    at emitTwo (events.js:87:13)
#    at ChildProcess.emit (events.js:172:7)
#    at handleMessage (internal/child_process.js:632:10)
#    at Pipe.channel.onread (internal/child_process.js:421:11)

[mathiask88]

@silverwind This error comes from OpenProcess in DebugProcess in node.cc because the child process is already terminated.The child process exits after stream.end() @ https://github.com/nodejs/io.js/blob/master/test/parallel/test-debug-port-from-cmdline.js#L11
Maybe it is related to #2149 but I think that one is caused by another reason.

[joaocgreis]

@mathiask88 I had the same problem, the debug build failed every time, exactly as yours. I investigated and found it is the same problem as #2149 . I opened a PR: #2186 . If you have the time, can you check if it fixes your issue?

[cjihrig]

Fixed in 2b4b600