-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Attempt to fix Sauce Labs where the tunnel closes early. #179
Conversation
Bootstrap seems to be experiencing the same problem, here is the latest build failing on master for commit 795d2208: Running "saucelabs-qunit:all" (saucelabs-qunit) task
=> Starting Tunnel to Sauce Labs
>> Connected to Saucelabs
1 / 13 tests started
2 / 13 tests started
3 / 13 tests started
4 / 13 tests started
5 / 13 tests started
6 / 13 tests started
7 / 13 tests started
8 / 13 tests started
9 / 13 tests started
10 / 13 tests started
11 / 13 tests started
12 / 13 tests started
13 / 13 tests started
=> Stopping Tunnel to Sauce Labs
>>
>> Error: POST https://saucelabs.com/rest/v1/bootstrap/js-tests failed.
>> at /home/travis/build/twbs/bootstrap/node_modules/grunt-saucelabs/src/utils.js:97:15
>> at _rejected (/home/travis/build/twbs/bootstrap/node_modules/grunt-saucelabs/node_modules/q/q.js:830:24)
>> at /home/travis/build/twbs/bootstrap/node_modules/grunt-saucelabs/node_modules/q/q.js:856:30
>> at Promise.when (/home/travis/build/twbs/bootstrap/node_modules/grunt-saucelabs/node_modules/q/q.js:1108:31)
>> at Promise.promise.promiseDispatch (/home/travis/build/twbs/bootstrap/node_modules/grunt-saucelabs/node_modules/q/q.js:774:41)
>> at /home/travis/build/twbs/bootstrap/node_modules/grunt-saucelabs/node_modules/q/q.js:590:44
>> at runSingle (/home/travis/build/twbs/bootstrap/node_modules/grunt-saucelabs/node_modules/q/q.js:123:13)
>> at flush (/home/travis/build/twbs/bootstrap/node_modules/grunt-saucelabs/node_modules/q/q.js:111:13)
>> at _combinedTickCallback (internal/process/next_tick.js:67:7)
>> at process._tickCallback (internal/process/next_tick.js:98:9)
>> Error: HTTP error (429)
>> at /home/travis/build/twbs/bootstrap/node_modules/grunt-saucelabs/src/utils.js:91:17
>> at _combinedTickCallback (internal/process/next_tick.js:67:7)
>> at process._tickCallback (internal/process/next_tick.js:98:9)
>> From previous event:
>> at Object.makeRequest (/home/travis/build/twbs/bootstrap/node_modules/grunt-saucelabs/src/utils.js:86:8)
>> at Job.start (/home/travis/build/twbs/bootstrap/node_modules/grunt-saucelabs/src/Job.js:86:8)
>> at getResult (/home/travis/build/twbs/bootstrap/node_modules/grunt-saucelabs/src/TestRunner.js:113:10)
Warning: Task "saucelabs-qunit:all" failed.� Use --force to continue.
Aborted due to warnings.
Execution Time (2016-04-14 23:05:36 UTC)
babel:dev 1.6s ▇▇▇ 6%
saucelabs-qunit:all 25.9s ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 94%
Total 27.5s
npm ERR! Test failed. See above for more details.
The command "npm test" exited with 1.
cache.2
store build cache
0.00s
10.45schanges detected, packing new archive
.
.
uploading archive
Done. Your build exited with 1. |
Let me know how your Sauce bug report fares. |
Response from Sauce Labs on case ID 38251: APR 18, 2016 | 05:00AM PDT
APR 18, 2016 | 11:28AM PDT
|
I have rerun the tests and all of them are passing for this PR now. |
This is the problem that is happening on CI (the tunnel closes early):
Attempt 1:
I suspect this might be related to the Grunt upgrade, but wasn't spot early because Sauce only runs in commits or PRs created by js-cookie members.Even reverting Grunt it keeps failing.
Inspecting the history, it seems that it started failing between e9e6176 (pass) and dbce759 (fails):
Here are the changes between both commits above, nothing touches any Sauce Labs dependency. We use fixed
package.json
dependency versions, so it is likely to be an upstream issue.Trying to restart the build 522 on Travis that was previously passing, so that we can be 100% certain that this problem is not in js-cookie...
Confirmed! Build 522 fails just by restarting it, it probably happens to all build. The problem is probably with Sauce Labs, creating bug report...
Report sent as a maximum priority level, case ID is 38251.