FormidableLabs / rowdy

A small, rambunctious WD.js / WebdriverIO configuration wrapper.
MIT License
28 stars 9 forks source link

Travis: Local selenium server start detection fails. #27

Closed ryan-roemer closed 9 years ago

ryan-roemer commented 9 years ago

Experiment: Took existing green build #80.2 with console text:

[SERVER] [stderr] 05:08:52.079 INFO - Started org.openqa.jetty.jetty.servlet.ServletHandler@1aaeead8
05:08:52.079 INFO - Started HttpContext[/wd,/wd]
[CLIENT] [cmd] CALL init({"browserName":"phantomjs"})
[CLIENT] [http] POST /session {"desiredCapabilities":{"browserName":"phantomjs","version":"","javascriptEnabled":true,"platform":"ANY"}}
[SERVER] [stderr] 05:08:52.084 INFO - Started SocketListener on 0.0.0.0:4444
05:08:52.085 INFO - Started org.openqa.jetty.jetty.Server@95b24dd
[SERVER] [stderr] 05:08:52.479 INFO - Executing: [new session: Capabilities [{platform=ANY, javascriptEnabled=true, browserName=phantomjs, version=}]])
[SERVER] [stderr] 05:08:52.499 INFO - Creating a new session for Capabilities [{platform=ANY, javascriptEnabled=true, browserName=phantomjs, version=}]

And rebuilt it:

[SERVER] [stderr] 23:50:38.630 INFO - RemoteWebDriver instances should connect to: http://127.0.0.2:4444/wd/hub
[SERVER] [stderr] 23:50:38.630 INFO - Selenium Server is up and running
[SERVER] [error] Error: Server start timeout
  1) "before all" hook
  0 passing (5s)
  1 failing
  1)  "before all" hook:
     Error: Server start timeout
      at null.<anonymous> (/home/travis/build/FormidableLabs/rowdy/lib/server.js:127:15)

And now it fails.

Looks like new "started" string in log Selenium Server is up and running.