Slow shutdown about karma-sauce-launcher

[jfroom]

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.

[jfroom]

Am experiencing a connection to iOS 6.1 which will not close on its own. I get this log:

Mobile Safari 6.0.0 (iOS 6.0): Executed 48 of 48 SUCCESS (42.064 secs / 0.783 secs)
INFO [launcher.sauce]: Shutting down Sauce Connect

But I have to manually cancel the test via Sauce's web interface.

[axemclion]

+1 to slow shutdown. Looks like the test is waiting for timeout of browsers before closing the connection ?

[johanneswuerbach]

I looks like the connection is closed before the browser loaded about:blank, which doesn't kill the browser.

[thom4parisot]

What is the state of that issue? Some builds are failing as nothing responds.

[nickradford]

+1 to slow shutdown. I see the heartbeat method is being run repeatedly, just an observation.

What's the state of this?

[thom4parisot]

I still encounter the issue: https://travis-ci.org/bbcrd/peaks.js/builds/29082024#L3048

Anything specific to do?

[johanneswuerbach]

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 ?

[bessdsv]

In new wersion used next code in lib/sauce_launcher.js
this.on('kill', function(done) {
if (sessionIsReady) {
....
driver.get('about:blank').catch().quit().nodeify(allDone);
sessionIsReady = false;
} else {
pendingCancellations++;
process.nextTick(allDone);
}
});
};

when i run karma with existing Virtual Tunnel and setted startConnect: false - all work excellent
but when i run with creating Virtual Tunel (default) tunnel not closing
and event driver.get('about:blank').catch().quit().nodeify(allDone);
do not fired

[givankin]

+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.

[transplier]

+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.

[transplier]

For us, it was a timing issue specifically in Chrome + Sauce. Seems like removing an iframe from within its own load event handler hangs Sauce + Chrome when the session is torn down, but only if that iframe is loading about:blank. Here is a minimal repro:

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.