-
Notifications
You must be signed in to change notification settings - Fork 102
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.
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
Slow shutdown #14
Comments
I just experienced a run from my local machine with two sauce connected browsers (chrome-linux, firefox-linux) where one 'finished' and the other hung. I killed the process manually after about a minute (trying to preserve my sauce credits). I ran the test two more times after this and both times exited successfully on its own. |
Am experiencing a connection to iOS 6.1 which will not close on its own. I get this log:
But I have to manually cancel the test via Sauce's web interface. |
+1 to slow shutdown. Looks like the test is waiting for timeout of browsers before closing the connection ? |
What is the state of that issue? Some builds are failing as nothing responds. |
+1 to slow shutdown. I see the What's the state of this? |
I still encounter the issue: https://travis-ci.org/bbcrd/peaks.js/builds/29082024#L3048 Anything specific to do? |
I use my fix #19 for a while now and haven't seen this error again. I'm not sure why this was never merged. @vojtajina ? |
In new wersion used next code in lib/sauce_launcher.js when i run karma with existing Virtual Tunnel and setted startConnect: false - all work excellent |
+1, the issue is very unfortunate because it costs money. It currently takes 15 minutes until SL shuts down the session when this happens. Which means 14 paid minutes wasted. |
+1 for us too. We currently have an active support ticket with SauceLabs to try and figure things out. Of note, the navigation to about:blank is indeed the culprit, but changing it to navigate to some other site instead (we used google) does not help. Will update as we learn more. |
For us, it was a timing issue specifically in Chrome + Sauce. Seems like removing an iframe from within its own it.only('hangs SauceLabs', function(done) {
// Minimally-sufficient set of operations to trigger bug.
// All lines are needed, except the call to done().
var iframe = $('<iframe>'); iframe
.appendTo('body')
.prop('src', 'about:blank') // Needs to be about:blank.
.on('load', function() {
iframe.remove();
done(); //Not strictly needed.
});
}); One of our tests does something similar. We've worked around the issue for now by loading a different site in the iframe. |
In several builds on Travis I see the exit after "INFO [launcher.sauce]: Shutting down Sauce Connect" takes 2-3 minutes. I'm not sure whether this is a karma or sauce connect launcher problem.
Do you have any idea? Browsers used are FF 20 (Win 8), IE 10 (Win 8) and Chrome (Linux)
The text was updated successfully, but these errors were encountered: