Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Behat failures with Selenium #1210

Closed
fiasco opened this issue Mar 20, 2017 · 0 comments
Closed

Behat failures with Selenium #1210

fiasco opened this issue Mar 20, 2017 · 0 comments

Comments

@fiasco
Copy link
Contributor

fiasco commented Mar 20, 2017

My system information:

  • Operating system type: TravisCI
  • Operating system version: TravisCI
  • BLT version: 8.6.15

When I run this command:

blt tests:selenium:launch

I get the following output:

blt > tests:selenium:launch:
blt > tests:selenium:kill:
     [echo] Killing any selenium processes that are already running.
     [echo] Launching Selenium standalone server.
    [touch] Creating /home/travis/build/EnergyAustralia/eaweb/reports/selenium2.log
     [echo] Selenium2 logs are being written to /home/travis/build/EnergyAustralia/eaweb/reports/selenium2.log.
     [echo] Waiting 15 seconds for Selenium standalone server (http://127.0.0.1:4444) to become available.
Possible malformed URL: http://127.0.0.1:4444/wd/hub
Possible malformed URL: http://127.0.0.1:4444/wd/hub
Possible malformed URL: http://127.0.0.1:4444/wd/hub
Possible malformed URL: http://127.0.0.1:4444/wd/hub
Possible malformed URL: http://127.0.0.1:4444/wd/hub
Possible malformed URL: http://127.0.0.1:4444/wd/hub
Possible malformed URL: http://127.0.0.1:4444/wd/hub
Possible malformed URL: http://127.0.0.1:4444/wd/hub
Possible malformed URL: http://127.0.0.1:4444/wd/hub
Possible malformed URL: http://127.0.0.1:4444/wd/hub
Possible malformed URL: http://127.0.0.1:4444/wd/hub
Possible malformed URL: http://127.0.0.1:4444/wd/hub
Possible malformed URL: http://127.0.0.1:4444/wd/hub
Possible malformed URL: http://127.0.0.1:4444/wd/hub
Possible malformed URL: http://127.0.0.1:4444/wd/hub
[phingcall] /home/travis/build/EnergyAustralia/eaweb/./vendor/acquia/blt/phing/tasks/tests.xml:129:8: /home/travis/build/EnergyAustralia/eaweb/./vendor/acquia/blt/phing/tasks/tests.xml:149:12: /home/travis/build/EnergyAustralia/eaweb/./vendor/acquia/blt/phing/tasks/tests.xml:152:18: Unable to start Selenium2 standalone server on http://127.0.0.1:4444/wd/hub.

After quite a bit of debugging on Travis CI (as this worked locally) I came across this post: http://stackoverflow.com/questions/32707201/selenium-standalone-server-not-starting which suggested changing java.security.egd to use /dev/urandom which worked a treat. It seems that in certain circumstances, /dev/random doesn't produce the entropy needed in Travis and this causes selenium to stall and BLT to timeout.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant