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
Platform: Linux 88a9dd2a2175 4.9.49-moby deps: update openssl to 1.0.1j #1 SMP Wed Sep 27 23:17:17 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
I am executing end to end tests using a chrome driver for selenium. Jest is the framework that executes the tests.
When running: node --inspect=0.0.0.0:9229 ./node_modules/.bin/jest -i
I have a series of end to end tests that run in a docker container against a chrome drive that is in a separate container. After the tests pass or fail I am hung on "Waiting for the debugger to disconnect..."
It never disconnects I was led to believe that this issue #12814 would fix his. However I am experiencing the same issue with the latest node version.
This does not seem to be a Node.js issue. Node "stuck" on this message means there is a frontend connected to the instance. In your case, I do not know what the frontend is. Please open a bug against the product that is acting as a frontend (Selenium?).
Activity
eugeneo commentedon Nov 27, 2017
This does not seem to be a Node.js issue. Node "stuck" on this message means there is a frontend connected to the instance. In your case, I do not know what the frontend is. Please open a bug against the product that is acting as a frontend (Selenium?).
ianguerin commentedon Nov 27, 2017
The front end connected to the node process is the Chrome Node.js Developer Tools.
eugeneo commentedon Nov 27, 2017