Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

sauce connect not proxying back properly #67

Open
cdaringe opened this issue Mar 14, 2017 · 5 comments
Open

sauce connect not proxying back properly #67

cdaringe opened this issue Mar 14, 2017 · 5 comments

Comments

@cdaringe
Copy link

problem statement

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

screen shot 2017-03-13 at 5 51 37 pm

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
Copy link
Author

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

@cdaringe
Copy link
Author

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

@cdaringe
Copy link
Author

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

@cdaringe
Copy link
Author

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

@cdaringe
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cdaringe