alexkras.com

  • Home
  • YouTube
  • Tech News TLDR
  • Top Posts
  • Resume
    • Projects
  • Contact
    • About

WebDriver.createSession Error in Protractor after Chrome Update

August 11, 2017 by Alex Kras Leave a Comment

Share this:

We run our protractor tests in Chrome instance via xvfb server. Last week after Chrome update to 60.0.3112.90, it began to fail with the following error.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
+ xvfb-run -d '--server-args=-screen 0 1280x1024x24' protractor protractor.config.js
[00:07:03] I/launcher - Running 1 instances of WebDriver
[00:07:03] I/direct - Using ChromeDriver directly...
[00:07:03] E/launcher - Server terminated early with status 1
[00:07:03] E/launcher - Error: Server terminated early with status 1
    at Error (native)
    at earlyTermination.catch.e (/usr/lib/node_modules/protractor/node_modules/selenium-webdriver/remote/index.js:252:52)
    at process._tickCallback (internal/process/next_tick.js:109:7)
From: Task: WebDriver.createSession()
    at Function.createSession (/usr/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:777:24)
    at Function.createSession (/usr/lib/node_modules/protractor/node_modules/selenium-webdriver/chrome.js:709:29)
    at Direct.getNewDriver (/usr/lib/node_modules/protractor/lib/driverProviders/direct.ts:90:25)
    at Runner.createBrowser (/usr/lib/node_modules/protractor/lib/runner.ts:225:39)
    at q.then.then (/usr/lib/node_modules/protractor/lib/runner.ts:391:27)
    at _fulfilled (/usr/lib/node_modules/protractor/node_modules/q/q.js:834:54)
    at self.promiseDispatch.done (/usr/lib/node_modules/protractor/node_modules/q/q.js:863:30)
    at Promise.promise.promiseDispatch (/usr/lib/node_modules/protractor/node_modules/q/q.js:796:13)
    at /usr/lib/node_modules/protractor/node_modules/q/q.js:556:49
    at runSingle (/usr/lib/node_modules/protractor/node_modules/q/q.js:137:13)
[00:07:03] E/launcher - Process exited with error code 199
Build step 'Execute shell' marked build as failure
 

The solution was to use an older version of Chrome driver for Selenium, via the following command:


1
2
3
webdriver-manager clean
webdriver-manager update --versions.chrome 2.28
 

Please Share:

Wanna see my pretty face and hear me ramble? Check out my YouTube channel 🙂

P.S. Check out Disrupted: My Misadventure in the Start-Up Bubble by Dan Lyons a co-producer and writer for the HBO series Silicon Valley (sponsored).


P.P.S. Let's connect on Twitter, Facebook or LinkedIn. You can also get updates via RSS Feed or the Email Form Bellow.
Follow @akras14

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

You may also like:
Share this:

Filed Under: JavaScript, Node.Js

Recent Post

  • Crunching Honeypot IP Data with Pandas and Python April 7, 2018
  • Introducing my YouTube Channel March 8, 2018
  • How to Restart Python Script after Exception and Run it Forever February 23, 2018
  • My Strategy for SQL Injection Attack February 21, 2018
  • Angular 1 Documentation Disappeared from Google Search Results February 16, 2018

Leave a Reply Cancel reply

Copyright © 2018 · eleven40 Pro Theme on Genesis Framework · WordPress · Log in