Opening test url times out over Sauce Connect

Functional tests for my open-source project that run on Sauce Labs have been failing since Aug 28.

I see that the browser is being sent a command to open the test url which is hosted in the CI environment. It’s expected to open it on localhost:8000 over sauce-connect. The attempt times out. I’ve confirmed that that old commits where this job passed, now fail when rerun, timing out for the same reason.

Support at Sauce Labs has looked at it but hasn’t offered much insight yet. I’m hoping someone here might be able to shed some light.

Here’s where the job has been failing. First test to run times out attempting to open the test url:
https://travis-ci.org/github/video-dev/hls.js/jobs/723642553#L1954

Sauce Connect seems to be setting up ok
https://travis-ci.org/github/video-dev/hls.js/jobs/723642553#L261

Here’s the logs from a week ago for the last job to pass (debug is not enabled in this one).
https://travis-ci.org/github/video-dev/hls.js/jobs/721389732

We’ve tested doing a GET request from travis to the test server and it returns a 200 status, so we’re just at a loss as to how to troubleshoot the request over sauce-connect. Thanks in advance for any help or tips!

1 Like

As I can see from https://app.saucelabs.com/tests/f61089848c884df6a77fd5454b5abe48#1, their browser tries to open data:, – which, of course, it can’t.

I’d ask Sauce support about where that erroneous URL comes from so you can track it to its origin.

Also seeing this for https://travis-ci.com/github/nickcmaynard/jsonschemalint, failing since 27th August. Seems to be attempting to connect to “localhost” and hanging…

We are having the same issue, also started on ~27th August (without making any changes in the Travis build script).

Not only the browser running on SauceLabs cannot access “localhost” server running on Travis, it cannot access any website (google.com etc.). Sauce Connect doctor is not reporting any significant issue.

Interesting thing I noticed is when I run the same script on forked repo, which uses travis-ci.org (not .com) it work seamlessly. So this may point to eg. some networking problem on travis-ci.com.

1 Like

The url bar reads data: but the selenium command to open the test at localhost was sent, and times out.

Yes, thats right.

Also when I take over control of the browser (started from Travis with Sauce Connect] in Sauce Labs dashboard, I can verify I cannot access basically any website from that browser.

Also when I take over control of the browser (started from Travis with Sauce Connect] in Sauce Labs dashboard, I can verify I cannot access basically any website from that browser.

Oh yeah? I found that clicking in the url bar showed the localhost address it’s trying to connect to, but it just doesn’t connect. I don’t know if I tried visiting any other sites.

Interesting thing I noticed is when I run the same script on forked repo, which uses travis-ci.org (not .com) it work seamlessly. So this may point to eg. some networking problem on travis-ci.com.

So should we be reporting this to support at travis? This space was the only course of action I found for reporting issues with travis-ci.

All,

Thanks for all the tips! I sent an email to support since this seems to be an issue in travis-ci.org with the sauce-connect add-on.

I got my tests running again by switching over from the sauce-connect travis add-on to npm sauce-connect-launcher. I deleted the addon section from my .travis.yml config, and I added async steps in the test runner before and after hooks to launch/close the module. Tests are running again. So far so good!

Imprint