Tunnel stuck on my setup

[mkxml]

Hello guys,

I'm having a problem here, I'm trying to test my program with saucelabs-mocha task but the connection to the sauce labs tunnel just keeps hanging, it says the testing process started by never close the tunnel and from the sauce labs console I get this odd message:

Automatic Tunnel: Jobs will not proxy through this tunnelunless the right identifier is provided.

I think it's something related to the tunnel ID, anyone else having this problem?

[Jonahss]

Hmm, that log message is expected if I'm not mistaken.
What happens if you manually start an unnamed sauce connect tunnel, and set 'tunneled' to false in the grunt task? This should cause grunt-saucelabs to not start a tunnel, but all your tests will be default utilize your tunnel.

[mkxml]

Now it does not open a tunnel to sauce labs but it still doesn't run the test.

Also I don't have any other tunnel to sauce labs, I'm expecting the grunt task to open one.

When running with tunneled: true the grunt log looks like this:

Running "connect:server" (connect) task
Started connect web server on http://0.0.0.0:8080

Running "saucelabs-mocha:all" (saucelabs-mocha) task

 1 / 1 tests started

When running with tunneled: false the grunt log looks like this:

Running "connect:server" (connect) task
Started connect web server on http://0.0.0.0:8080

Running "saucelabs-mocha:all" (saucelabs-mocha) task
=> Starting Tunnel to Sauce Labs
>> Connected to Saucelabs

 1 / 1 tests started

Both cases never complete the test. When running mocha locally everything looks fine.

[evilaliv3]

this happens to me also on openpgpjs: https://travis-ci.org/evilaliv3/openpgpjs

how did you manage to solve your issue @mkautzmann ?

[mkxml]

@evilaliv3 I actually didn't, my project is mainly web component focused so I decided to use Polymer's Web Component Tester, that project has a plugin for sauce labs called wct-sauce. I still don't know why their method is working on my environment and grunt-saucelabs is not.