-
Notifications
You must be signed in to change notification settings - Fork 23
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
IE11 disconnects after some time #8
Comments
Well, in IE, anything can happen. I did a tons of stuff to make IE (8-10) stable on our Travis + SL, however I didn't have any issues with IE11. You can try canary Karma (0.11), which has these features. You can configure: Are you using Jasmine? If so, can you try |
Thanks. Yes, I'm using Jasmine so I'll try it, the I'll report here with my findings. |
This patch tries to auto-detect 64-bit IE by checking for the appropriate environment variables. It also improves reliability of the tests by disabling extensions and using "InPrivate" mode to ignore existing user data. Addresses karma-runner#1, karma-runner#2, karma-runner#4, and possibly karma-runner#8.
IE 11 has some problems: karma-runner/karma-ie-launcher#8
There still seem to be problems. Any ideas where we can investigate further? |
My unit tests take much longer to run in IE than in Chrome/Firefox (where they take 30-40 seconds). After some time over 2 minutes IE11 gets disconnected:
This makes it impossible for me to test on IE... Is there anything else that could trigger the disconnection besides the timeout? Any way to troubleshoot it?
EDIT: it seems it's not based on time but on some specific tests. It almost always fails after 181 or 180 tests from 414. There is, however, nothing demanding in these particular tests that wasn't already run in earlier tests due to
beforeEach
blocks. If I exclude the offending module, tests fail after 9 minutes, near the end.Why is it so? IMO the total disconnection should never happen. If there is a bug, an error should be thrown instead of just disconnecting from the browser which says nothing about what's wrong.
The text was updated successfully, but these errors were encountered: