grunt-saucelabs: Post to status endpoint is failing

[This is a duplicate of #193 in hopes of an open issue getting more attention]

I’m getting the following error when I try to run this task from travis:

Running "saucelabs-jasmine:all" (saucelabs-jasmine) task
Verifying property saucelabs-jasmine.all exists in config...OK
File: [no files]
Options: username="agrc-deq-enviro", key="...", tunneled=false, identifier="222125027", pollInterval=2000, statusCheckAttempts=500, testname="deq-enviro", browsers=[{"browserName":"safari","platform":"OS X 10.10"},{"browserName":"firefox","platform":"Windows 8.1"},{"browserName":"chrome","platform":"Windows 8.1"},{"browserName":"internet explorer","platform":"Windows 8.1","version":"11"},{"browserName":"internet explorer","platform":"Windows 8","version":"10"},{"browserName":"internet explorer","platform":"Windows 7","version":"9"}], tunnelArgs=[], sauceConfig={"max-duration":10800}, maxRetries=10, urls=["http://localhost:8001_SpecRunner.html"], tunnelTimeout=120, build="95467903", maxPollRetries=10, throttled=5
 1 / 6 tests started
 2 / 6 tests started
 3 / 6 tests started
 4 / 6 tests started
 5 / 6 tests started
 6 / 6 tests started
>> Error: POST https://saucelabs.com/rest/v1/agrc-deq-enviro/js-tests failed.
>>     at /home/travis/build/agrc/deq-enviro/node_modules/grunt-saucelabs/src/utils.js:97:15
>>     at _rejected (/home/travis/build/agrc/deq-enviro/node_modules/grunt-saucelabs/node_modules/q/q.js:830:24)
>>     at /home/travis/build/agrc/deq-enviro/node_modules/grunt-saucelabs/node_modules/q/q.js:856:30
>>     at Promise.when (/home/travis/build/agrc/deq-enviro/node_modules/grunt-saucelabs/node_modules/q/q.js:1108:31)
>>     at Promise.promise.promiseDispatch (/home/travis/build/agrc/deq-enviro/node_modules/grunt-saucelabs/node_modules/q/q.js:774:41)
>>     at /home/travis/build/agrc/deq-enviro/node_modules/grunt-saucelabs/node_modules/q/q.js:590:44
>>     at runSingle (/home/travis/build/agrc/deq-enviro/node_modules/grunt-saucelabs/node_modules/q/q.js:123:13)
>>     at flush (/home/travis/build/agrc/deq-enviro/node_modules/grunt-saucelabs/node_modules/q/q.js:111:13)
>>     at doNTCallback0 (node.js:419:9)
>>     at process._tickCallback (node.js:348:13)
>>     Error: HTTP error (400)
>>         at /home/travis/build/agrc/deq-enviro/node_modules/grunt-saucelabs/src/utils.js:91:17
>>     From previous event:
>>         at Object.makeRequest (/home/travis/build/agrc/deq-enviro/node_modules/grunt-saucelabs/src/utils.js:86:8)
>>         at Job.start (/home/travis/build/agrc/deq-enviro/node_modules/grunt-saucelabs/src/Job.js:86:8)
>>         at getResult (/home/travis/build/agrc/deq-enviro/node_modules/grunt-saucelabs/src/TestRunner.js:113:10)
Warning: Task "saucelabs-jasmine:all" failed. Use --force to continue.

I am using the sauce_connect addon in .travis.yml. Would this cause any issues?

addons:
  sauce_connect:
    username: agrc-deq-enviro
    access_key:
        secure: ...

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 17

Most upvoted comments

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?

eugenet8k on Apr 14, 2016

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

leeyeh on Apr 28, 2016

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 notifications@github.com wrote:

Same for us!

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/axemclion/grunt-saucelabs/issues/200#issuecomment-211443499

Jonahss on Apr 18, 2016

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.

kevin-brown on Apr 17, 2016