IE6 freeze on sauce Labs #983
Comments
|
I have the same freeze with karma, did you find a solution ? |
|
also freezes w/o any tests at all |
|
I would vote for Karma stopping support for IE6. Then we close this issue and have a happier life 🍨 |
|
The problem is due to socket.io not properly falling back to If you're using grunt-karma, an easy workaround is to separate the task into multiple batches (which is a good thing to do anyway if you test in more than 3 browsers due to the limited concurrency and the browsers timing out otherwise anyway), like so: var sauceBrowsers = require( './tests/saucelabs.browsers.js' );
grunt.initConfig( {
..
karma: {
options: {
frameworks: [ 'qunit' ],
files: [
'dist/app.js',
'test/testrunner.js',
'test/unit/*.js'
],
preprocessors: {
'dist/*.js': [ 'coverage' ]
},
reporters: [ 'dots' ],
singleRun: true,
autoWatch: false,
customLaunchers: sauceBrowsers,
..
ci1: {
browsers: [ 'slChrome', 'slFirefox', 'slIE11' ]
},
ci2: {
browsers: [ 'slSafari5Mac', 'slIE9', 'slIE6' ],
// Support IE6: Default socket.io transport doesn't work on IE6
transports: [ 'jsonp-polling' ]
},
phantom: {
browsers: [ 'PhantomJS' ],
reporters: [ 'dots', 'coverage' ],
coverageReporter: { reporters: [
{
type: 'html',
dir: 'dist/coverage/'
},
{
type: 'text-summary'
}
] }
},
bg: {
browsers: [ 'PhantomJS', 'Firefox', 'Chrome' ],
singleRun: false,
background: true
}
},
_watch: {
files: [
'.{jscsrc,jshintignore,jshintrc}',
'<%= files.scipts %>'
],
tasks: [ '_test', 'karma:bg:run' ]
}
..
} );
grunt.renameTask( 'watch', '_watch' );
grunt.registerTask( 'build', .. );
grunt.registerTask( '_test', [ 'build', 'jshint', 'jscs'] );
grunt.registerTask( 'test', [ '_test', 'karma:phantom'] );
grunt.registerTask( 'ci', [ 'test', 'karma:ci1', 'karma:ci2' ] );
grunt.registerTask( 'watch', [ 'karma:bg:start', '_watch' ] ); |
|
👍 thanks! |
|
👍 |
|
Karma v0.13 has removed It seems that, if you want IE6 support, you need to use Karma v0.12. This also seems to be the case with IE7 too. |
|
@riggerthegeek you should be able to add any transport that socket.io supports through the |
|
@dignifiedquire Yeah, it's working as expected. It's just that in v0.13, |
|
Okay, so the transport |
|
It looks like it should work, but I doesn't. I added the I've had a brief look whilst at work, but it's not as easy as we'd first hoped. I'll see fork and see if I can fix it, but might not be immediately |
* Revert Karma v0.13 back to v0.12. Karma v0.13 upgrades Socket.IO to 1.0 which drops support for jsonp-polling (and xhr-polling or websockets are not supported in older browsers). They now provide this feature via: transport=polling and forceJSONP=true, however Karma hasn't expose that option yet. Upstream: karma-runner/karma#983 Was causing tests to time out as the transports array effectively became empty leaving the client no way to communicate with the server. Follows-up e76f759. * Drop Safari 5 in favour of Safari 6. OSX 10.6 is end-of-life as of July 2015. See <https://support.saucelabs.com/customer/portal/articles/2061176-end-of-life-for-osx-10-6> Launching OSX 10.6/Safari 5 was causing an error: "The environment you requested was unavailable" Change-Id: If88d648b657d8a571beb7991805f8af8bd547975
|
Noticed the same regression at Wikimedia when trying to upgrade to Karma v0.13. It just times out. There is no error of any kind when using When using Karma v0.13, setting |
|
👍 😕 |
|
Tracking IE compat in #1564 so closing this issue |
Follows-up 16a5f8c which downgraded Karma back to 0.12. The issue with IE<9 was fixed in Karma v0.13.20. * karma-runner/karma#983 * karma-runner/karma#1564 Also makes use of the new 'concurrency' option introduced in Karma v0.13.12. This makes the test run a bit faster by starting browser #4 as soon as one of browsers 1-2-3 is finished, etc. Once we drop ES3 and IE6 support, we can remove ci1/ci2 split. Also: * PhantomJS node-wrapper package got renamed, which is required by karma-phantomjs-launcher. * Can't upgrade grunt-contrib-uglify because the new version depends on a newer version of npm package 'gzip-size' which dropped support for Node 0.10 (which Wikimedia CI still uses). Change-Id: I08bed822273bca2d2d80fa765fc0b0fbba4d997a
Hi all!
I have been trying to test my javascript with Grunt/Karma/Jasmine on SauceLabs and I get a recurrent error:
internet explorer 6 (Windows XP) on SauceLabs have not captured in 120000 ms, killing.Is this a know issue? is there a "right way to do this?"
All other IE work on my tests, just IE6 doesn't. I Can see on SauceLabs "Karma is running" but nothing more happens.
Had issue open at karma-sauce-launcher, but seems the problem might be Karma.
I know IE6 is almost dead, but still would like to know why this hangs.
The text was updated successfully, but these errors were encountered: