New Error: Could not connect to Sauce Labs API: Error: read ECONNRESET

Question

New Error: Could not connect to Sauce Labs API: Error: read ECONNRESET

Closed this issue 10 years ago · 31 comments

All our builds are failing with the following error now

Could not connect to Sauce Labs API: Error: read ECONNRESET

I am not quite sure where the error is coming from yet

cvrebert commented 10 years ago

Exactly.

LaurentGoderre commented 10 years ago

Same here

Answer 1 · 2014-12-11T07:05:46.000Z

I'm also experiencing this problem with 1 throttled option.

Answer 2 · 2014-12-12T19:53:36.000Z

Still experiencing this problem? It could have been a temporary outage.

Answer 3 · 2014-12-12T20:59:48.000Z

Could have been but what is really weird is, and that could be because of the SauceLabs API, all test would pass but the task would fail giving this message. I will keep testing to see if it's still occurring.

Answer 4 · 2014-12-12T21:27:05.000Z

Ah, I think someone else encountered this and they submitted a PR we just merged. Try the newest version of grunt-saucelabs.

Answer 5 · 2014-12-12T21:33:16.000Z

Thanks! Though debugging intermittent issues are always the most difficult

Answer 6 · 2014-12-12T23:00:32.000Z

I'm running into the same issue myself while running tests. The new retry code should fix it, but I'll try to see whats up with the API...

Answer 7 · 2014-12-12T23:11:55.000Z

Also seeing some weird ordering in the output. Not sure whether it indicates anything in particular:

 10 / 12 tests started
 11 / 12 tests started
=> Stopping Tunnel to Sauce Labs
 12 / 12 tests started
>> Could not connect to Sauce Labs API: Error: read ECONNRESET
Warning: Task "saucelabs-qunit:all" failed.� Use --force to continue.

Answer 8 · 2014-12-12T23:17:21.000Z

Thanks. A bit less concerned about that one but could reveal something
interesting.

On Fri, Dec 12, 2014 at 3:11 PM, Chris Rebert notifications@github.com
wrote:

Also seeing some weird ordering in the output. Not sure whether it
indicates anything in particular:

10 / 12 tests started
11 / 12 tests started
=> Stopping Tunnel to Sauce Labs
12 / 12 tests started

Could not connect to Sauce Labs API: Error: read ECONNRESET
Warning: Task "saucelabs-qunit:all" failed. Use --force to continue.

—
Reply to this email directly or view it on GitHub
#174 (comment)
.

Answer 9 · 2015-01-04T21:44:01.000Z

I'm having this problem too. Is it a server-side problem?

Answer 10 · 2015-01-05T19:42:47.000Z

I'm going on the assumption that it is a server-side problem, and we're trying to nail down a simpler reproduction case.

Answer 11 · 2015-01-05T19:58:34.000Z

Trying to narrow it down too. Will let you know what I find.

Answer 12 · 2015-01-05T19:59:18.000Z

^.^

On Mon, Jan 5, 2015 at 11:58 AM, Laurent Goderre notifications@github.com
wrote:

Trying to narrow it down too. Will let you know what I find.

—
Reply to this email directly or view it on GitHub
#174 (comment)
.

Answer 13 · 2015-01-05T20:02:11.000Z

Would be great if there was retry logic for this.. 🙏

Answer 14 · 2015-01-05T20:05:20.000Z

There is a retry for timeout but not for this.

Answer 15 · 2015-01-05T20:15:49.000Z

@cvrebert what about this: #175

Answer 16 · 2015-01-05T20:16:20.000Z

The thing is since this basically an unhandled exception, there is no way to know what caused the issue. It just happens that for this bug retrying works but it's not guaranteed for all unhandled exceptions

Answer 17 · 2015-01-05T20:17:11.000Z

@Jonahss I am not sure it would work because when the error occur it doesn't poll anymore

Answer 18 · 2015-01-05T20:23:21.000Z

@Jonahss Ah! I'll give that a shot.

Answer 19 · 2015-01-08T17:23:18.000Z

Is everyone who got this error using Sauce Connect tunnels?

Answer 20 · 2015-01-08T17:24:47.000Z

I use tunnels and got this error.

Answer 21 · 2015-01-14T23:23:08.000Z

Using Sauce Connect and also getting this error. Does seem to hit me when running >= 3 browsers or so. SauceLabs reporting The Sauce VMs failed to start the browser or device For more info, please check https://docs.saucelabs.com/reference/troubleshooting-common-error-messages/ in the interface despite the browsers I'm using being fully supported:

[
    {
        "browserName": "firefox",
        "platform": "Windows 8.1",
        "version": "15",
        "deviceName": ""
    },
    {
        "browserName": "chrome",
        "platform": "Windows 8.1",
        "version": "26",
        "deviceName": ""
    },
    {
        "browserName": "internet explorer",
        "platform": "Windows 8.1",
        "version": "11",
        "deviceName": ""
    },
    {
        "browserName": "firefox",
        "platform": "OS X 10.6",
        "version": "15",
        "deviceName": ""
    }
]

Answer 22 · 2015-01-14T23:24:25.000Z

Feels as though one test encountered The Sauce VMs failed to start the browser or device For more info, please check https://docs.saucelabs.com/reference/troubleshooting-common-error-messages/ and the tunnel was immediately disconnected instead of allowing other tests to complete first.

Answer 23 · 2015-01-15T19:41:50.000Z

Yeah, we should check the logic for closing tunnels, we should make sure the tunnel isn't closed until all tests have fully completed.

Answer 24 · 2015-01-15T19:58:28.000Z

Shouldn't that be a separate issue though?

Answer 25 · 2015-01-15T20:00:10.000Z

The error is different, but the way we handle tunnels might be responsible
for the same thing we see here.

On Thu, Jan 15, 2015 at 11:58 AM, Laurent Goderre notifications@github.com
wrote:

Shouldn't that be a separate issue though?

—
Reply to this email directly or view it on GitHub
#174 (comment)
.

Answer 26 · 2015-01-15T20:01:27.000Z

Not sure, the suggested PR seems to be fixing this specific issue

Answer 27 · 2015-01-15T20:43:16.000Z

See the discussion here. @gvas found that specific versions of Node.js cause issues.

Answer 28 · 2015-01-20T15:23:29.000Z

This should be fixed in version 8.5.0

comment here if you still encounter ECONNRESET errors after updating.

Answer 29 · 2015-01-20T16:15:42.000Z

Thanks everyone for the help!!