Chromedriver frequently hangs when attempting to start a new session. #87
Description
Using the standalone-chrome or node-chrome images, I often observe a timeout when attempting to launch a new Chrome session.
Steps to reproduce:
- launch a standalone chrome instance:
docker run -d --name chrome selenium/standalone-chrome:2.47.1 - build the test container:
docker build -t selenium/test:local ./Test - run the repeat test script:
./test-repeat.sh chrome - If necessary, repeat steps 1 and 3 until the problem is observed
Note:
In order to narrow the focus of the test to launching new sessions, you may want to temporarily modify Test/smoke-test.js to omit the part of the test that tries navigating to github.com after starting the session. After modifying the script, make sure to rebuild the selenium/test:local image to pick up the changes.
Expected results:
All 50 sessions launch and quit successfully - the test passes.
Actual results:
One of the session launch commands will hang indefinitely.
Docker host: boot2docker v1.7.0 (Tiny Core Linux)