cdaringe commented 7 years ago

problem statement

saucelabs isn't proxying back properly to my CI testem server

discussion

all env vars are set as necessary on my CI server
sc is running
the testem server is serving the test content

rof@railsonfire:~/clone$ ps aux | grep $(cat sc_client.pid)
rof       17113  0.0  0.0 176488  7016 ?        Ssl  00:46   0:02 /home/rof/src/github.com/cdaringe/browser-csrf/node_modules/sauce-connect-launcher/sc/sc-4.3.16-linux/bin/sc -u wa11-e -k <KEY> --pidfile sc_client.pid --tunnel-identifier 23399054 --readyfile /tmp/sc-launcher-readyfile
rof       18267  0.0  0.0  21252  2220 pts/7    S+   00:51   0:00 grep --color=auto 17113
## ^ cool, `sc` is running!

rof@railsonfire:~/clone$ curl localhost:8080/8556
<!doctype html>
<html>
<head>
<title>Test'em</title>
<link rel="stylesheet" href="//cdnjs.cloudflare.com/ajax/libs/mocha/2.3.4/mocha.css">
<script src="//cdnjs.cloudflare.com/ajax/libs/mocha/2.3.4/mocha.js"></script>
<script src="/testem.js"></script>
<script>mocha.setup('bdd')</script>
<script src="test/index.bundle.js"></script>

</head>
<body>
<div id="mocha"></div>
<script>
mocha.run()
</script>
</body>
</html>

cool, so testem server is up, sc is up, but maybe 8080 isnt the right port?

cdaringe commented 7 years ago

i tried running testem ci --port 4445, but the same failure mode occurs :/

cdaringe commented 7 years ago

for what its worth, i'm using codeship. it could have something to do w/ their network config?

cdaringe commented 7 years ago

son of a gun, i found this text in the testem automated test jobs: 'Sauce Connect Proxy Disabled'

cdaringe commented 7 years ago

does saucie need to specify the tunnel for each test to use on-run?

cdaringe commented 7 years ago

ah ha! in CI, i set CI_BUILD_NUMBER='' and it worked!! something is borked w/ assigning a tunnel ID to jobs.

johanneswuerbach / saucie

sauce connect not proxying back properly #67

problem statement

discussion