-
Notifications
You must be signed in to change notification settings - Fork 2.3k
ECONNREFUSED after server shutdown with grunt-protractor-runner #1123
Comments
Clarification - does this only occur using Phantom.js? |
@DavidTanner I just updated to v1.0.0, and it started happening exactly the same behavior, and only with phantomJS. |
@juliemr Yes, just phantomjs and for me only in ubuntu.
|
Facing the same issue with Chrome. It works OK on version 0.24.2. I am running this with grunt task using https://www.npmjs.org/package/grunt-protractor-runner. |
How can I downgrade my version, updating the 'package.json' file ? |
Just change the version to ~0.24.2 or ^0.24.2 depending on your node version, then npm install to get the version you want. |
+1 here with Chrome on both OS X and Ubuntu. "Needs: more info" - please tell us what more information you need. |
+1 with Chrome on Windows 7. grunt-protractor-runner: ^1.14 |
+1 with Chrome on Mac OS Lion ==============(fixed) |
+1 with Chrome on Mac OS Yosemite console report https://gist.github.com/orloffv/f255d93c9b577b0f784c |
OK - I think there might be multiple issues at work here. Let's ignore the phantom issues - people who aren't using phantom, can you share your configuration? I cannot reproduce this. |
i'm running Windows 8.1 x64. Gruntfile.js =
package.json =
protractorConfig.js =
Output from tests =
Note we are running grunt from F# Fake, but this should have no bearing on this error. If i change my protractorConfig to use
then i do not get the error. |
I'm beginning to suspect this is an issue with grunt-protractor-runner, since everyone having the problem is using it. Anyone NOT using grunt-protractor-runner have this problem? |
Pretty sure you are right @juliemr. Have raised teerapap/grunt-protractor-runner#99 |
please reference teerapap/grunt-protractor-runner#99 and teerapap/grunt-protractor-runner#100 I managed to resolve this |
If any one has got the solution to this problem, please provide the details. I am facing same issue on mac osx. Running "protractor:webdriver" (protractor) task /Users/sjoshi/Documents/SJWorkspace/GDAClientAutomationTest/node_modules/protractor/node_modules/selenium-webdriver/http/index.js:145 Also if there are any specific versions that are compatible and works for you, please specify them. |
Looks like this is resolved. Closing. |
Using version 1.0.0 I get an error message that the connection was refused. This is similiar to issue #85. I found someone had similiar issues in http://stackoverflow.com/questions/21382962/when-running-protractor-with-phantomjs-browser-only-able-to-run-tests-once and changed my version to 0.24.2 and the issue went away.
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)
node_modules/protractor/node_modules/selenium-webdriver/http/index.js:136
callback(new Error(message));
^
Error: ECONNREFUSED connect ECONNREFUSED
at ClientRequest. (node_modules/protractor/node_modules/selenium-webdriver/http/index.js:136:16)
at ClientRequest.EventEmitter.emit (events.js:95:17)
at Socket.socketErrorListener (http.js:1547:9)
at Socket.EventEmitter.emit (events.js:95:17)
at net.js:440:14
at process._tickCallback (node.js:415:13)
==== async task ====
WebDriver.quit()
The text was updated successfully, but these errors were encountered: