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 |
P.S. Please consider sharing this post or donating a dollar to help support this site.
Leave a Reply