js-cookie: Running tests in Sauce Labs no longer working

All we get to see is a tunnel being started and immediately after it is closed:

$ grunt saucelabs
Running "uglify:build" (uglify) task
>> 2 files created 7.77 kB → 3.28 kB

Running "connect:build-sauce" (connect) task
Started connect web server on http://localhost:9999

Running "saucelabs-qunit:all" (saucelabs-qunit) task
=> Starting Tunnel to Sauce Labs
>> 
=> Stopping Tunnel to Sauce Labs
>> Error closing tunnel

This happens both in Travis as well as when running grunt saucelabs locally while providing the saucelabs credentials via environment. Tried with a newly created access key.

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 23 (23 by maintainers)

Most upvoted comments

This seems to be the same problem: https://github.com/webdriverio/webdriverio/issues/3754

So the workaround is to or use 10.13 or use the local ip of the machine that hosts the site.

Ok, we’re running tests again in Saucelabs in the first place, but on macOS 10.14 they seem to be unstable (getting a “500 Internal Server Error”) when accessing the qunit test suite: https://app.saucelabs.com/tests/801c906a9a0c4561a6676c60e3f71128#51

In macOS 10.13 it would just hang: https://app.saucelabs.com/tests/8cb7c6aa630f4e64baadc0124acc945e#2

Not sure what I did to make them run… updating the binaries didn’t seem to do it and it worked by coincidence. 🤷

maybe the sauce-tunnel package needs the latest binary

Yes, that seems to be the case. Started to run tests successfully with a patched, local sauce-tunnel package.

…maybe the sauce-tunnel package needs the latest binary, it’s using 4.3.16 (https://github.com/jmreidy/sauce-tunnel#v250), current one is 4.5.4.

Maybe it has to do with grunt-saucelabs using version 1.5.0 of

Doesn’t even seem to be used…

Maybe it has to do with grunt-saucelabs using version 1.5.0 of https://www.npmjs.com/package/saucelabs

=> https://github.com/axemclion/grunt-saucelabs/blob/127cac287947399be79b5d6c96493dff5fb45184/package.json#L32

There’s a much newer version out. We could try to define our own task for running the tests via tunnel…

Using the same credentials I am able to set up a tunnel manually using just Saucelabs’ sc downloadable binary.

Maybe it’s time to revive https://github.com/js-cookie/js-cookie/pull/409 and figure out why we can’t run tests on iOS devices in Browserstack… oh my, stuck between two hard rocks it seems.

Thanks @FagnerMartinsBrack – tested with the newly created acccount, as well as with another private one where I still had trial minutes left. None of them work, so at least I’m sure that it wasn’t a problem with some stale access key.