You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is currently an issue with the test test-cluster-disconnect-handles.js where the debugger gets an EADDRINUSE error and does not exit and therefore does not release the port it is using. This causes an issue when running
As the port is not released and tests continue to run causing a large number of tests to fail with EADDRINUSE too.
Sample output:
imran@tp-iqbali ~/node/node_main ./out/Release/node --debug=12346. --expose_internals test/parallel/test-cluster-disconnect-handles.js
Debugger listening on port 12346
Error: listen EADDRINUSE :::12346
at Object.exports._errnoException (util.js:915:11)
at exports._exceptionWithHostPort (util.js:938:20)
at Agent.Server._listen2 (net.js:1236:14)
at listen (net.js:1272:10)
at Agent.Server.listen (net.js:1369:5)
at Object.start (_debug_agent.js:21:9)
at startup (node.js:72:9)
at node.js:976:3
(Process stays running until explicitly killed)
There is currently an issue with the test test-cluster-disconnect-handles.js where the debugger gets an EADDRINUSE error and does not exit and therefore does not release the port it is using. This causes an issue when running
As the port is not released and tests continue to run causing a large number of tests to fail with EADDRINUSE too.
Sample output:
Output from lsof before running the test:
And after
Making sure I have no running node instances before running the test
And after running the test
I have ran into this issue on multiple machines.
This is on linux x86-64, with e4e5b13 checked out from master branch
Using ubuntu 14.04
output of uname -a
The text was updated successfully, but these errors were encountered: