Why doesn't Chrome 59-Beta with real Headless function work with Protractor?

I wanted to use the latest beta version of Chrome 59 with the --headless option to test our Angular project (github.com/h-da/geli).

I was able to use karma with the new GC beta, but I could not start protractor with the new GC beta. I tried to launch a protractor on Jenkins and on my local vagrant car, both gave me the same error:

  [17:13:12] I/direct - Using ChromeDriver directly... [17:14:12] E/launcher - chrome not reachable (Driver info: chromedriver=2.29.461571 (8a88bbe0775e2a23afda0ceaf2ef7ee74e822cc5),platform=Linux 4.4.0-51-generic x86_64) [17:14:12] E/launcher - WebDriverError: chrome not reachable (Driver info: chromedriver=2.29.461571 (8a88bbe0775e2a23afda0ceaf2ef7ee74e822cc5),platform=Linux 4.4.0-51-generic x86_64) at Object.checkLegacyResponse (/home/travis/build/[secure]/geli/app/webFrontend/node_modules/selenium-webdriver/lib/error.js:505:15) at parseHttpResponse (/home/travis/build/[secure]/geli/app/webFrontend/node_modules/selenium-webdriver/lib/http.js:509:13) at doSend.then.response (/home/travis/build/[secure]/geli/app/webFrontend/node_modules/selenium-webdriver/lib/http.js:440:13) at process._tickCallback (internal/process/next_tick.js:109:7) From: Task: WebDriver.createSession() at Function.createSession (/home/travis/build/[secure]/geli/app/webFrontend/node_modules/selenium-webdriver/lib/webdriver.js:777:24) at Function.createSession (/home/travis/build/[secure]/geli/app/webFrontend/node_modules/selenium-webdriver/chrome.js:709:29) at Direct.getNewDriver (/home/travis/build/[secure]/geli/app/webFrontend/node_modules/protractor/lib/driverProviders/direct.ts:90:25) at Runner.createBrowser (/home/travis/build/[secure]/geli/app/webFrontend/node_modules/protractor/lib/runner.ts:225:39) at q.then.then (/home/travis/build/[secure]/geli/app/webFrontend/node_modules/protractor/lib/runner.ts:391:27) at _fulfilled (/home/travis/build/[secure]/geli/app/webFrontend/node_modules/protractor/node_modules/q/q.js:834:54) at self.promiseDispatch.done (/home/travis/build/[secure]/geli/app/webFrontend/node_modules/protractor/node_modules/q/q.js:863:30) at Promise.promise.promiseDispatch (/home/travis/build/[secure]/geli/app/webFrontend/node_modules/protractor/node_modules/q/q.js:796:13) at /home/travis/build/[secure]/geli/app/webFrontend/node_modules/protractor/node_modules/q/q.js:556:49 at runSingle (/home/travis/build/[secure]/geli/app/webFrontend/node_modules/protractor/node_modules/q/q.js:137:13) at flush (/home/travis/build/[secure]/geli/app/webFrontend/node_modules/protractor/node_modules/q/q.js:125:13) at _combinedTickCallback (internal/process/next_tick.js:73:7) at process._tickCallback (internal/process/next_tick.js:104:9) [17:14:12] E/launcher - Process exited with error code 199 

Here you can see Jenkins Build: travis-ci.org/khase/geli/builds/232136348 and the fron code that Build is here: https://github.com/khase/geli/tree/1fe73b4aac9b , and the protractor file is here https : //github.com/khase/geli/blob/1fe73b4aac9b5c8c0b39b93a8fe40283dd3a92f7/app/webFrontend/protractor.conf.js

Now my question is: why am I getting chrome not reachable ?

Thanks guys a lot :)

PS: We forked our current project to check out CI => / khase / geli stuff

+5
source share

All Articles