400 Bad Request on Windows 8

[ghguy]

We tried a sample functional test and got this weird error:

C:\XXXXXXXXXXXXX\test\js\functional\intern>node_modules\.bin\intern-runner config=tests/intern.js
Listening on 0.0.0.0:9000
Starting tunnel...
Sauce Connect 4.3, build 1285 bd6579a
Using no proxy for connecting to Sauce Labs REST API.
**********
************************************************
A newer version of Sauce Connect (build 1600) is available!
Download it here:
https://saucelabs.com/downloads/sc-4.3.5-win32.zip
**********************************************************
Started scp
roxy on port 57766.
Starting secure remote tunnel V
M...
30 Nov 18:32:5
hite">
<center><h1>400 Bad Request</h1></center>
<hr><center>nginx</center>
</body>
</html>
Finished! Deleting tunnel.
Error: JSON parse error on line 1: '[' or '{' expected near '<'.
Error: JSON parse error on line 1: '[' or '{' expected near '<'.
  at reject  <node_modules\intern\node_modules\digdug\SauceLabsTunnel.js:354:17>

  at readStartupMessage  <node_modules\intern\node_modules\digdug\SauceLabsTunne
l.js:382:12>
  at <node_modules\intern\node_modules\digdug\SauceLabsTunnel.js:435:12>
  at Array.some  <native>
  at Socket.<anonymous>  <node_modules\intern\node_modules\digdug\SauceLabsTunne
l.js:429:21>
  at Socket.emit  <events.js:117:20>
  at Socket.<anonymous>  <_stream_readable.js:748:14>
  at Socket.emit  <events.js:92:17>
  at emitReadable_  <_stream_readable.js:410:10>
  at emitReadable  <_stream_readable.js:406:5>

It works fine on Mac OS 10.9, however. Any insight into this?

Thanks!

[csnover]

Thanks for the report, but this is not an Intern bug. That error is coming from a Sauce Labs server when contacted by their own tunnel software, so you’ll need to complain at them. I’ve verified that Intern is working fine against Sauce Labs in Windows 8.1 at the moment. Their service has been even more unreliable than usual lately, so this was probably a temporary issue. I would recommend choosing one of the other providers instead, at least until Sauce gets their act together. Thanks!

[ghguy]

It's not Windows 8.1, it's Windows 8. Have you tested against 8 instead of just closing this ticket?

Tested again today, same issue.

[ghguy]

Another offshore person helped us to identify that the same box, running Windows 8 with Protractor is working fine against SauceLabs using the same userid and key. At this point, we are thinking it is more like Intern issue(s) rather than Windows 8 or SauceLabs.

Care to re-open this ticket to look into it again? +1:

[jason0x43]

I just ran a number of functional tests on a Sauce Windows 8 / IE10 box using Intern 2.1.0, both from a Mac 10.10 system and a Windows 8 system. The tests ran without error in all cases, so it seems unlikely to be an inherent problem with Intern.

If you'd like to open a question on Stack Overflow we can look into this in more detail.

[ghguy]

We will record a screen cast or two to show you the error as well as the working with protractor on the same box, if that helps to rule out SaurceLabs. Meanwhile, let us know if you need anything else/logs or any troubleshooting tips that will help us all.

Thanks for your understanding and such a great product! :)

[ghguy]

Here you go http://tinyurl.com/kn5azga.

HTH