Post to status endpoint is failing about grunt-saucelabs HOT 17 CLOSED

Hi @stdavis, did you guys figure out the problem with this exception? I just started to face the same:

Error: POST https://saucelabs.com/rest/v1/#my_user_name#/js-tests failed.

Randomly without any recent changes in my grunt config. Was it something on the SauceLabs side?

from grunt-saucelabs.

I just started hitting this issue the other day and it looks like it wasn't a one-time issue.

The configuration we use can be found here, and we're currently using version 8.6.2.

from grunt-saucelabs.

We've got people contacting customer support at Sauce Labs about this, so
will start working on a fix, unless an open source contributor wants to
look at it first.

On Mon, Apr 18, 2016 at 8:55 AM, Laurent Goderre [email protected]
wrote:

Same for us!

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#200 (comment)

from grunt-saucelabs.

@eugenet8k the problem disappeared couple of days ago. Have you try to restart your test?

from grunt-saucelabs.

You're posting to "https://saucelabs.com/rest/v1/agrc-deq-enviro/js-tests" but that's not the saucelabs api endpoint. the argc-deq-enviro clause doesn't look like it should be there. Any idea where it came from?

from grunt-saucelabs.

That's my sauce username.

from grunt-saucelabs.

ah. my bad. hm hm

from grunt-saucelabs.

Does this happen for every test? Or is it an occasional bug.

from grunt-saucelabs.

Yes, every time I do a build on travis this happens currently. Maybe related to the fact that I'm using this project to run my jasmine unit tests and intern to run functional tests in the same build? Not sure.

most recent build
.travis.yml
GruntFile.js

Thanks for taking another look at this.

from grunt-saucelabs.

@eugenet8k When did that POST request happen? There was a Saucelabs outage last night.

from grunt-saucelabs.

@Jonahss I am having this problem since last night and it is still reproducible. The SauceLabs support recommends to do not use tunneling (weird) and make sure that config doesn't have "identifier" parameter, which I believe is being added by grunt-saucelabs. I am trying to figure out now.

from grunt-saucelabs.

Ah ok. Maybe grunt-saucelabs was updated to the newest version of Sauce Connect, which may have eliminated the concept of "named" tunnels.

from grunt-saucelabs.

@eugenet8k: I eventually gave up and converted all of my unit tests to intern.

from grunt-saucelabs.

Same here, I'm using v8.6.2.
Here is my config: https://github.com/leeyeh/js-realtime-sdk/blob/0dd20626e014908a8802c35a2627d0d8b40db1ab/Gruntfile.js#L225-L238

from grunt-saucelabs.

Same for us!

from grunt-saucelabs.

@Jonahss have you guys got any updates on who's going to fix the problem? It seems now there is literally no way anyone can use grunt-saucelabs to run unit tests using tunneling in SauceLabs cloud. I contacted support and they recommended me to work out the problem with this repo owners.

from grunt-saucelabs.

@leeyeh Yeah, confirming that. Now it works.

from grunt-saucelabs.