I would like to catch/handle this Error:
07:28:34 > protractor protractor.config.js
07:28:34 [07:28:34] I/launcher - Running 1 instances of WebDriver
07:28:34 [07:28:34] I/direct - Using ChromeDriver directly...
07:28:35 [07:28:34] E/launcher - unknown error: Chrome failed to start: exited abnormally
07:28:35 (unknown error: DevToolsActivePort file doesn't exist)
07:28:35 (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
07:28:35 (Driver info: chromedriver=2.41.578700 (2f1ed5f9343c13f73144538f15c00b370eda6706),platform=Linux 3.10.0-862.14.4.el7.x86_64 x86_64)
07:28:35 [07:28:34] E/launcher - WebDriverError: unknown error: Chrome failed to start: exited abnormally
07:28:35 (unknown error: DevToolsActivePort file doesn't exist)
07:28:35 (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
07:28:35 (Driver info: chromedriver=2.41.578700 (2f1ed5f9343c13f73144538f15c00b370eda6706),platform=Linux 3.10.0-862.14.4.el7.x86_64 x86_64)
07:28:35 at Object.checkLegacyResponse (/opt/jenkins/workspace/monitoring-app/node_modules/selenium-webdriver/lib/error.js:546:15)
07:28:35 at parseHttpResponse (/opt/jenkins/workspace/monitoring-app/node_modules/selenium-webdriver/lib/http.js:509:13)
07:28:35 at doSend.then.response (/opt/jenkins/workspace/monitoring-app/node_modules/selenium-webdriver/lib/http.js:441:30)
07:28:35 at process._tickCallback (internal/process/next_tick.js:68:7)
07:28:35 From: Task: WebDriver.createSession()
07:28:35 at Function.createSession
[...]
07:28:35 [07:28:34] E/launcher - Process exited with error code 199
07:28:35 npm ERR! Test failed. See above for more details.
Where can I do that? In the protractor.config.js?
Related
Chrome 93 was released recently. Roughly around this time (Aug 31 at 4PM Central) our end-to-end tests started failing. These tests leverage Protractor, they are running via TeamCity, on a Windows build agent that has Chrome 93 installed.
We have tried to force a 93.x and a 92.x version of chromedriver. Both produce this timeout below. We can run these e2e tests locally without issue. Any suggestions?
[10:23:38] I/launcher - Running 1 instances of WebDriver
10:23:38 [10:23:38] I/direct - Using ChromeDriver directly...
10:33:40 [10:33:40] E/launcher - session not created
10:33:40 from timeout: Timed out receiving message from renderer: 600.000
10:33:40 (Session info: chrome=93.0.4577.63)
10:33:40 (Driver info: chromedriver=93.0.4577.15 (660fc11082ba57405eca2e8c49c3e1af756fbfae-refs/branch-heads/4577#{#203}),platform=Windows NT 10.0.14393 x86_64)
10:33:40 [10:33:40] E/launcher - SessionNotCreatedError: session not created
10:33:40 from timeout: Timed out receiving message from renderer: 600.000
10:33:40 (Session info: chrome=93.0.4577.63)
10:33:40 (Driver info: chromedriver=93.0.4577.15 (660fc11082ba57405eca2e8c49c3e1af756fbfae-refs/branch-heads/4577#{#203}),platform=Windows NT 10.0.14393 x86_64)
10:33:40 at Object.checkLegacyResponse (C:\BuildAgent\work\f3ee5d88fcfb5472\node_modules\selenium-webdriver\lib\error.js:546:15)
10:33:40 at parseHttpResponse (C:\BuildAgent\work\f3ee5d88fcfb5472\node_modules\selenium-webdriver\lib\http.js:509:13)
10:33:40 at C:\BuildAgent\work\f3ee5d88fcfb5472\node_modules\selenium-webdriver\lib\http.js:441:30
10:33:40 at processTicksAndRejections (internal/process/task_queues.js:93:5)
10:33:40 From: Task: WebDriver.createSession()
10:33:40 at Function.createSession (C:\BuildAgent\work\f3ee5d88fcfb5472\node_modules\selenium-webdriver\lib\webdriver.js:769:24)
10:33:40 at Function.createSession (C:\BuildAgent\work\f3ee5d88fcfb5472\node_modules\selenium-webdriver\chrome.js:761:15)
10:33:40 at Direct.getNewDriver (C:\BuildAgent\work\f3ee5d88fcfb5472\node_modules\protractor\built\driverProviders\direct.js:77:33)
10:33:40 at Runner.createBrowser (C:\BuildAgent\work\f3ee5d88fcfb5472\node_modules\protractor\built\runner.js:195:43)
10:33:40 at C:\BuildAgent\work\f3ee5d88fcfb5472\node_modules\protractor\built\runner.js:339:29
10:33:40 at _fulfilled (C:\BuildAgent\work\f3ee5d88fcfb5472\node_modules\protractor\node_modules\q\q.js:834:54)
10:33:40 at C:\BuildAgent\work\f3ee5d88fcfb5472\node_modules\protractor\node_modules\q\q.js:863:30
10:33:40 at Promise.promise.promiseDispatch (C:\BuildAgent\work\f3ee5d88fcfb5472\node_modules\protractor\node_modules\q\q.js:796:13)
10:33:40 at C:\BuildAgent\work\f3ee5d88fcfb5472\node_modules\protractor\node_modules\q\q.js:556:49
10:33:40 at runSingle (C:\BuildAgent\work\f3ee5d88fcfb5472\node_modules\protractor\node_modules\q\q.js:137:13)
10:33:40 [10:33:40] E/launcher - Process exited with error code 199
It's not an identical question/situation, but there is a bunch of helpful insight in this SO post.
We're using protractor, so for us the fix was adding the --disable-gpu argument below, which was also hinted at a bunch in the above SO post.
chromeOptions: {
args: [
'--disable-gpu'
]
}
Not sure why this was needed as-of Chrome 93 for us, but it is also listed in the Protractor browser setup (claiming this is needed as of Chrome 58).
As of Chrome 58 you also need to set --disable-gpu, though this may
change in future versions.
I was able to fix the problem try using the following options (not nice, but it works...):
chromeOptions.addArguments("no-sandbox");
chromeOptions.addArguments("disable-infobars");
chromeOptions.addArguments("disable-dev-shm-usage");
chromeOptions.addArguments("disable-browser-side-navigation");
chromeOptions.addArguments("disable-gpu");
chromeOptions.addArguments("--dns-prefetch-disable");
chromeOptions.addArguments("disable-extensions");
chromeOptions.addArguments("force-device-scale-factor=1");
chromeOptions.setPageLoadStrategy(PageLoadStrategy.NORMAL);
chromeOptions.addArguments("enable-features=NetworkServiceInProcess");
chromeOptions.addArguments("--aggressive-cache-discard");
chromeOptions.addArguments("--disable-cache");
chromeOptions.addArguments("--disable-application-cache");
chromeOptions.addArguments("--disable-offline-load-stale-cache");
chromeOptions.addArguments("start-maximized");
chromeOptions.addArguments("lang=de");
chromeOptions.addArguments("allow-running-insecure-content");
chromeOptions.addArguments("inprivate");
I have an angularjs project that I am trying to set up protractor with. I'll eventually be doing it in angular 5 as well but this current project is angularjs. I'm on Windows Server 2016. The steps I took were:
Installed protractor globally
npm install protractor -g
Updated webdriver-manager
webdriver-manager update
Started webdriver-manager
webdriver-manager start
My protractor.conf.js located in in test folder
exports.config = {
seleniumAddress: 'http://localhost:4444/wd/hub',
specs: ['e2e/**/*.js'],
capabilities: {
browserName: 'chrome'
}
};
When I run protractor from commandline
protractor test/protractor.conf.js
I get the following error:
E:\DemoApp>protractor test/protractor.conf.js
[16:36:25] I/launcher - Running 1 instances of WebDriver
[16:36:25] I/hosted - Using the selenium server at http://localhost:4444/wd/hub
[16:36:45] E/launcher - Timed out waiting for driver server to start.
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
System info: host: 'APC', ip: 'x.x.x.x', os.name: 'Windows Server 2016', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_231'
Driver info: driver.version: unknown
[16:36:45] E/launcher - WebDriverError: Timed out waiting for driver server to start.
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
System info: host: 'APC', ip: 'x.x.x.x', os.name: 'Windows Server 2016', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_231'
Driver info: driver.version: unknown
at Object.checkLegacyResponse (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\error.js:546:15)
at parseHttpResponse (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:509:13)
at C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:441:30
at processTicksAndRejections (internal/process/task_queues.js:93:5)
From: Task: WebDriver.createSession()
at Function.createSession (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver.js:769:24)
at Function.createSession (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\chrome.js:761:15)
at createDriver (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\index.js:170:33)
at Builder.build (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\index.js:626:16)
at Hosted.getNewDriver (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\built\driverProviders\driverProvider.js:53:33)
at Runner.createBrowser (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\built\runner.js:195:43)
at C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\built\runner.js:339:29
at _fulfilled (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:834:54)
at C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:863:30
at Promise.promise.promiseDispatch (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:796:13)
[16:36:45] E/launcher - Process exited with error code 199
Here's what webdriver-manager reported when erroring
E:\DemoApp>webdriver-manager start
[16:33:35] I/start - java -Dwebdriver.gecko.driver=C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\webdriver-manager\selenium\geckodriver-v0.26.0.exe -Dwebdriver.chrome.driver=C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\webdriver-manager\selenium\chromedriver_79.0.3945.36.exe -jar C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\webdriver-manager\selenium\selenium-server-standalone-3.141.59.jar -port 4444
[16:33:35] I/start - seleniumProcess.pid: 3728
16:33:36.252 INFO [GridLauncherV3.parse] - Selenium server version: 3.141.59, revision: e82be7d358
16:33:36.351 INFO [GridLauncherV3.lambda$buildLaunchers$3] - Launching a standalone Selenium Server on port 4444
2020-01-29 16:33:36.408:INFO::main: Logging initialized #415ms to org.seleniumhq.jetty9.util.log.StdErrLog
16:33:36.689 INFO [WebDriverServlet.<init>] - Initialising WebDriverServlet
16:33:36.841 INFO [SeleniumServer.boot] - Selenium Server is up and running on port 4444
16:36:25.573 INFO [ActiveSessionFactory.apply] - Capabilities are: {
"browserName": "chrome",
"count": 1
}
16:36:25.575 INFO [ActiveSessionFactory.lambda$apply$11] - Matched factory org.openqa.selenium.grid.session.remote.ServicedSession$Factory (provider: org.openqa.selenium.chrome.ChromeDriverService)
16:36:45.599 ERROR [OsProcess.checkForError] - org.apache.commons.exec.ExecuteException: Process exited with an error: -1073741819 (Exit value: -1073741819)
webdriver-manager says I am up-to-date as well
E:\DemoApp>webdriver-manager update
[16:46:25] I/update - selenium standalone: file exists C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\webdriver-manager\selenium\selenium-server-standalone-3.141.59.jar
[16:46:25] I/update - selenium standalone: selenium-server-standalone-3.141.59.jar up to date
[16:46:25] I/update - chromedriver: file exists C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\webdriver-manager\selenium\chromedriver_79.0.3945.36.zip
[16:46:25] I/update - chromedriver: unzipping chromedriver_79.0.3945.36.zip
[16:46:25] I/update - chromedriver: chromedriver_79.0.3945.36.exe up to date
[16:46:25] I/update - geckodriver: file exists C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\webdriver-manager\selenium\geckodriver-v0.26.0.zip
[16:46:25] I/update - geckodriver: unzipping geckodriver-v0.26.0.zip
[16:46:26] I/update - geckodriver: geckodriver-v0.26.0.exe up to date
What am I doing wrong here?
try with the below command to start the webdriver instead of webdriver-manager start
java -Dwebdriver.chrome.driver="chromedriver.exe" -jar selenium-server-standalone-3.141.59.jar -port 4444
Face the following error
Google Chrome - 67.0
chromedriver - chromedriver_2.40
selenium standalone - selenium-server-standalone-3.12.0.jar
linux - CentOS Linux release 7.3
Protractor - 5.1.2
Nodejs - v6.14.2
config.ts
chrome: {
seleniumAddress: 'http://localhost:4444/wd/hub',
directConnect: true,
browserName: 'chrome',
chromeOptions:{
args: ['--headless','--disable-gpu','--disable-dev-shm-usage','--no-sandbox','window-size=1024,768']
}
10:37:07.923 [10:37:07] I/launcher - Running 1 instances of WebDriver
10:37:07.923 [10:37:07] I/hosted - Using the selenium server at http://localhost:4444/wd/hub
10:38:09.409 [10:38:09] E/launcher - unknown error: Chrome failed to start: crashed
10:38:09.409 (Driver info: chromedriver=2.40.565383 (76257d1ab79276b2d53ee976b2c3e3b9f335cde7),platform=Linux 3.10.0-514.26.2.el7.x86_64 x86_64) (WARNING: The server did not provide any stacktrace information)
10:38:09.409 Command duration or timeout: 60.39 seconds
10:38:09.409 Build info: version: '3.12.0', revision: '7c6e0b3', time: '2018-05-08T15:15:08.936Z'
10:38:09.409 System info: host: 'sigmagoagt-po-a1p.sys.comcast.net', ip: '147.191.72.189', os.name: 'Linux', os.arch: 'amd64', os.version: '3.10.0-514.26.2.el7.x86_64', java.version: '1.8.0_40'
10:38:09.410 Driver info: driver.version: unknown
10:38:09.410 [10:38:09] E/launcher - WebDriverError: unknown error: Chrome failed to start: crashed
10:38:09.410 (Driver info: chromedriver=2.40.565383 (76257d1ab79276b2d53ee976b2c3e3b9f335cde7),platform=Linux 3.10.0-514.26.2.el7.x86_64 x86_64) (WARNING: The server did not provide any stacktrace information)
10:38:09.410 Command duration or timeout: 60.39 seconds
10:38:09.410 Build info: version: '3.12.0', revision: '7c6e0b3', time: '2018-05-08T15:15:08.936Z'
10:38:09.411 System info: host: 'sigmagoagt-po-a1p.sys.comcast.net', ip: '147.191.72.189', os.name: 'Linux', os.arch: 'amd64', os.version: '3.10.0-514.26.2.el7.x86_64', java.version: '1.8.0_40'
10:38:09.411 Driver info: driver.version: unknown
10:38:09.411 at WebDriverError (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/selenium-webdriver/lib/error.js:27:5)
10:38:09.411 at Object.checkLegacyResponse (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/selenium-webdriver/lib/error.js:505:15)
10:38:09.411 at parseHttpResponse (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/selenium-webdriver/lib/http.js:509:13)
10:38:09.412 at doSend.then.response (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/selenium-webdriver/lib/http.js:440:13)
10:38:09.412 at process._tickCallback (internal/process/next_tick.js:109:7)
10:38:09.412 From: Task: WebDriver.createSession()
10:38:09.412 at Function.createSession (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/selenium-webdriver/lib/webdriver.js:777:24)
10:38:09.412 at Function.createSession (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/selenium-webdriver/chrome.js:709:29)
10:38:09.412 at createDriver (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/selenium-webdriver/index.js:167:33)
10:38:09.412 at Builder.build (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/selenium-webdriver/index.js:623:16)
10:38:09.413 at Hosted.getNewDriver (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/protractor/lib/driverProviders/driverProvider.ts:60:29)
10:38:09.413 at Runner.createBrowser (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/protractor/lib/runner.ts:225:39)
10:38:09.413 at q.then.then (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/protractor/lib/runner.ts:391:27)
10:38:09.413 at _fulfilled (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/protractor/node_modules/q/q.js:834:54)
10:38:09.413 at self.promiseDispatch.done (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/protractor/node_modules/q/q.js:863:30)
10:38:09.413 at Promise.promise.promiseDispatch (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/protractor/node_modules/q/q.js:796:13)
10:38:09.414 at /app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/protractor/node_modules/q/q.js:556:49
10:38:09.414 at runSingle (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/protractor/node_modules/q/q.js:137:13)
10:38:09.414 at flush (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/protractor/node_modules/q/q.js:125:13)
10:38:09.414 at _combinedTickCallback (internal/process/next_tick.js:73:7)
10:38:09.414 at process._tickCallback (internal/process/next_tick.js:104:9)
You can run tests using selenium server or run them directly on browser. You should remove one of :
seleniumAddress: 'http://localhost:4444/wd/hub',
or
directConnect: true,
Uninstalling and re-installation of Chrome in centOS machine solved the issue. Followed installation procedure available in "https://intoli.com/blog/installing-google-chrome-on-centos/". Thank you.
I am getting the error below when trying to run Protractor test against chrome.
session not created exception: Chrome version must be >= 59.0.3071.0
[11:42:23] E/launcher - session not created exception: Chrome version must be >= 59.0.3071.0 (Driver info: chromedriver=2.32.498550 (9dec58e66c31bcc53a9ce3c7226f0c1c5810906a),platform=Windows NT 6.1.7601 SP1 x86_64) (WARNING: The server did not provide
any stacktrace information) Command duration or timeout: 6.44 seconds Build info: version: '3.5.3', revision: 'a88d25fe6b', time: '2017-08-29T12:54:15.039Z' System info: host: 'PC328569', ip: '10.25.227.179', os.name: 'Windows 7', os.arch: 'amd64', os.version:
'6.1', java.version: '1.8.0_121' Driver info: driver.version: unknown [11:42:23] E/launcher - SessionNotCreatedError: session not created exception: Chrome version must be >= 59.0.3071.0 (Driver info: chromedriver=2.32.498550 (9dec58e66c31bcc53a9ce3c7226f0c1c5810906a),platform=Windows
NT 6.1.7601 SP1 x86_64) (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 6.44 seconds Build info: version: '3.5.3', revision: 'a88d25fe6b', time: '2017-08-29T12:54:15.039Z' System info: host: 'PC328569', ip:
'10.25.227.179', os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.8.0_121' Driver info: driver.version: unknown at WebDriverError (D:\Balachander\DailyScript\node_modules\selenium-webdriver\lib\error.js:27:5) at SessionNotCreatedError
(D:\Balachander\DailyScript\node_modules\selenium-webdriver\lib\error.js:214:5) at Object.checkLegacyResponse (D:\Balachander\DailyScript\node_modules\selenium-webdriver\lib\error.js:505:15) at parseHttpResponse (D:\Balachander\DailyScript\node_modules\selenium-webdriver\lib\http.js:509:13)
at doSend.then.response (D:\Balachander\DailyScript\node_modules\selenium-webdriver\lib\http.js:440:13) at process._tickCallback (internal/process/next_tick.js:103:7) From: Task: WebDriver.createSession() at Function.createSession (D:\Balachander\DailyScript\node_modules\selenium-webdriver\lib\webdriver.js:777:24)
at Function.createSession (D:\Balachander\DailyScript\node_modules\selenium-webdriver\chrome.js:709:29) at createDriver (D:\Balachander\DailyScript\node_modules\selenium-webdriver\index.js:167:33) at Builder.build (D:\Balachander\DailyScript\node_modules\selenium-webdriver\index.js:623:16)
at Hosted.getNewDriver (D:\Balachander\DailyScript\node_modules\protractor\lib\driverProviders\driverProvider.ts:60:29) at Runner.createBrowser (D:\Balachander\DailyScript\node_modules\protractor\lib\runner.ts:225:39) at q.then.then (D:\Balachander\DailyScript\node_modules\protractor\lib\runner.ts:391:27)
at _fulfilled (D:\Balachander\DailyScript\node_modules\q\q.js:834:54) at self.promiseDispatch.done (D:\Balachander\DailyScript\node_modules\q\q.js:863:30) at Promise.promise.promiseDispatch (D:\Balachander\DailyScript\node_modules\q\q.js:796:13) [11:42:23]
E/launcher - Process exited with error code 199
Versions of the executables used:
webdriver manager - 12.0.6
protractor - 5.1.2
chrome driver - 2.32
Java - 1.8
What I have tried:
1.Updating the webdriver to latest version
npm update -g protractor
webdriver-manager update
2.Editing Protractor's config file: node_modules/protractor/config.json
Changing the chrome driver version to whatever you need. eg. "chromedriver": "2.24".Run webdriver-manager update.
But for some reason webdriver-manager always uses chrome driver 2.32.
Any help or suggestion is appreciated. Thanks.
As per Below references you need to update your actual installed chrome.
Update chrome by :- About Google Chrome
Menu -> Help ->
Refer :-
https://github.com/appveyor/ci/issues/1600
Chromedriver error "Chrome version must be >= 52" using Nightwatch
Hope it will help you :)
This is what i am getting in console
nothing change in npm or in code ,nothing found on internet related to this issue
[14:29:48] I/local - Starting selenium standalone server...
[14:29:48] I/launcher - Running 1 instances of WebDriver
[14:29:50] I/local - Selenium standalone server started at http://192.168.80.132:49611/wd/hub
D:\Workspace\pen\content\node_modules\protractor\node_modules\selenium-webdriver\error.js:27
super(opt_error);
^
WebDriverError: Connection reset
at WebDriverError (D:\Workspace\pen\content\node_modules\protractor\node_modules\selenium-webdriver\error.js:27:10)
at Object.checkLegacyResponse (D:\Workspace\pen\content\node_modules\protractor\node_modules\selenium-webdriver\erro
r.js:580:13)
at D:\Workspace\pen\content\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver.js:64:13
at Promise.invokeCallback_ (D:\Workspace\pen\content\node_modules\protractor\node_modules\selenium-webdriver\lib\pro
mise.js:1329:14)
at TaskQueue.execute_ (D:\Workspace\pen\content\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.
js:2790:14)
at TaskQueue.executeNext_ (D:\Workspace\pen\content\node_modules\protractor\node_modules\selenium-webdriver\lib\prom
ise.js:2773:21)
at D:\Workspace\pen\content\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2652:27
at D:\Workspace\pen\content\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:639:7
at process._tickCallback (node.js:369:9)
From: Task: WebDriver.createSession()
at acquireSession (D:\Workspace\pen\content\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver.js
:62:22)
at Function.createSession (D:\Workspace\pen\content\node_modules\protractor\node_modules\selenium-webdriver\lib\webd
river.js:295:12)
at Builder.build (D:\Workspace\pen\content\node_modules\protractor\node_modules\selenium-webdriver\builder.js:458:24
)
at Local.DriverProvider.getNewDriver (D:\Workspace\pen\content\node_modules\protractor\built\driverProviders\driverP
rovider.js:37:33)
at Runner.createBrowser (D:\Workspace\pen\content\node_modules\protractor\built\runner.js:182:43)
at D:\Workspace\pen\content\node_modules\protractor\built\runner.js:255:30
at _fulfilled (D:\Workspace\pen\content\node_modules\q\q.js:834:54)
at self.promiseDispatch.done (D:\Workspace\pen\content\node_modules\q\q.js:863:30)
at Promise.promise.promiseDispatch (D:\Workspace\pen\content\node_modules\q\q.js:796:13)
at D:\Workspace\pen\content\node_modules\q\q.js:604:44
[14:29:54] E/launcher - Process exited with error code 1
npm ERR! Windows_NT 6.3.9600