-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Karma doesnt respects the capture timeout for IE #605
Karma doesnt respects the capture timeout for IE #605
Comments
Closed by mistake |
The problem is IE_BIN points by default to Karma thinks it crashed (as it exited before capturing) and therefore starts it again. I'm closing this, as it is duplicate of #369 Also, see #429 |
Hi, I am getting error below: WARN [config]: "/" is proxied, you should probably change urlRoot to avoid conflicts INFO [launcher]: Trying to start IE again. INFO [launcher]: Trying to start IE again. INFO [launcher]: Trying to start IE again. I set the path to IE_BIN to C:\Program Files (x86)\Internet Explorer\iexplore.exe |
I have trying to execute tests in 3 browsers (Chrome, Firefox, IE). The capture timeout is set to the default value (60000).
When I run Karma, it claims that Explorer have failed to start even before Chrome and Firefox were opened.
Here is a log example:
INFO [karma]: Karma server started at http://localhost:9876/
INFO [launcher]: Starting browser Chrome
INFO [launcher]: Starting browser Firefox
INFO [launcher]: Starting browser IE
ERROR [launcher]: Cannot start IE
INFO [launcher]: Trying to start IE again.
ERROR [launcher]: Cannot start IE
INFO [launcher]: Trying to start IE again.
ERROR [launcher]: Cannot start IE
INFO [IE 10.0 (Windows)]: Connected on socket id bReo06CvJ8UWiIKAP8CE
INFO [IE 10.0 (Windows)]: Connected on socket id kApe7Od2JczJbBcaP8CF
INFO [IE 10.0 (Windows)]: Connected on socket id Ar8uOfRvU7rb53-fP8CG
INFO [Firefox 21.0 (Windows)]: Connected on socket id IyA7oUcBoxO7RSaEP8CH
INFO [Chrome 27.0 (Windows)]: Connected on socket id 9oVMw4LczaCTaNjIP8CI
The text was updated successfully, but these errors were encountered: