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

504 Gateway Time-out not handled properly #95

Closed
cvrebert opened this issue Jan 16, 2014 · 1 comment
Closed

504 Gateway Time-out not handled properly #95

cvrebert opened this issue Jan 16, 2014 · 1 comment

Comments

@cvrebert
Copy link
Contributor

See https://travis-ci.org/twbs/bootstrap/jobs/17089345

Running "saucelabs-qunit:all" (saucelabs-qunit) task
=> Connecting to Saucelabs ...
=> Looks like there are existing tunnels to Sauce Labs, need to kill them. TunnelID:<html>
<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx/0.7.62</center>
</body>
</html>
=> Killing tunnel <
=> Killing tunnel !
=> Killing tunnel D
=> Killing tunnel O
=> Killing tunnel C
=> Killing tunnel T
@Jonahss
Copy link
Collaborator

Jonahss commented Jan 16, 2014

@cvrebert grunt-saucelabs just forwards the log from the sauce-tunnel module. I'll go log an issue over at that project, but more likely the source is inside the sauce-connect jar.

@Jonahss Jonahss mentioned this issue Jan 16, 2014
Closed
@Jonahss Jonahss closed this as completed Jan 16, 2014
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
2 participants
@cvrebert @Jonahss