saucelabs/sauce_ruby — Issue #27: Sauce-Connect.jar failures aren't detected cleanly
Author: rtyler
Created: 2012-03-01 22:21:12+00:00
State: open

When running the `TestConnect.test_error_flag` the following

```
2012-03-01 14:14:08.835:INFO::jetty-7.x.y-SNAPSHOT
2012-03-01 14:14:08.865:INFO::Started SelectChannelConnector@0.0.0.0:50512
.---------------------------------------------------.
| Have questions or need help with Sauce Connect? |
| Contact us: http://support.saucelabs.com/forums |
| Terms of Service: http://saucelabs.com/tos |
-----------------------------------------------------
2012-03-01 14:14:08,878 - / Starting \
2012-03-01 14:14:08,882 - Please wait for "You may start your tests" to start your tests.
2012-03-01 14:14:08,892 - Forwarding: ['sauce-connect.proxy']:['80'] -> 127.0.0.1:['50512']
2012-03-01 14:14:08,910 - Succesfully connected to local server 127.0.0.1:50512 in 11ms
Traceback (most recent call last):
File "__pyclasspath__/java_urllib2.py", line 41, in open
IOException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://saucelabs.com/rest/v1/fail/tunnels?full=1
```

The Jython exception is raised and then the process errors out immediately :(