Open p-p-m opened 9 years ago
+1 on Ubuntu 12.04
Same here on Windows 8. Also using grunt-protractor-webdriver
in combination with grunt-protractor-runner
.
Seems only to happen with Chrome and IE, but not with Firefox.
Also seeing this on Windows 8.1. Adding
keepAlive = true
to my grunt-protractor-webdriver options resolves it, but that seems like a shaky workaround.
same problem here, it only works if I set keepAlive to true, but the exception is thrown anyway:
... tests green ...
Finished in 10.233 seconds
1 test, 2 assertions, 0 failures
Session deleted: Going to shut down the Selenium server
Shutting down Selenium server: http://127.0.0.1:4444
Shut down Selenium server: http://127.0.0.1:4444 (OKOK)
/path/to/src/node_modules/protractor/node_modules/selenium-webdriver/http/index.js:145
callback(new Error(message));
^
Error: ECONNREFUSED connect ECONNREFUSED
...
[launcher] Process exited with error code 1
>>
>> Test failed but keep the grunt process alive.
Done, without errors.
directConnect: true
Solves the problem for Chrome and FF.
What is the latest way to handle this on Windows 10? Setting keepAlive and directConnect to true to not resolve the ECONNREFUSED error. I can only get around this by manually starting a webdriver in a new command window but that defies the purpose of the grunt runner.
I have an error, similar to error described in issue#99(https://github.com/teerapap/grunt-protractor-runner/issues/99)
This error occurs then I use
grunt-protractor-runner
withgrunt-protractor-webdriver
and setkeepAlive
to false. As I understandgrunt-protractor-webdriver
shuts down Selenium too early and this causes error.