Skip to content
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

Closed
rzio opened this issue Jun 27, 2013 · 3 comments · May be fixed by Chadzzz1/karma#8, ilw4r/karma#11, Chadzzz1/karma#9 or Chadzzz1/karma#13
Closed

Karma doesnt respects the capture timeout for IE #605

rzio opened this issue Jun 27, 2013 · 3 comments · May be fixed by Chadzzz1/karma#8, ilw4r/karma#11, Chadzzz1/karma#9 or Chadzzz1/karma#13
Labels

Comments

@rzio
Copy link

rzio commented Jun 27, 2013

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

@rzio rzio closed this as completed Jun 30, 2013
@rzio rzio reopened this Jun 30, 2013
@rzio
Copy link
Author

rzio commented Jun 30, 2013

Closed by mistake

@vojtajina
Copy link
Contributor

The problem is IE_BIN points by default to Program Files\something and that does not start the browser, instead it forks a new process with Program File (x86)\something and therefore the first process immediately exits.

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
If you think it's not the same issue, feel free to re-open.

@agdev
Copy link

agdev commented Jul 15, 2013

Hi,
I have the same issue.
OS: Win 7 x 64
Karma: v0.9.3
Grunt:grunt-cli v0.1.9
grunt v0.4.1

I am getting error below:

WARN [config]: "/" is proxied, you should probably change urlRoot to avoid conflicts
INFO [karma]: Karma v0.9.3 server started at http://localhost:9876/

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 [launcher]: Trying to start IE again.
ERROR [launcher]: Cannot start IE

I set the path to IE_BIN to C:\Program Files (x86)\Internet Explorer\iexplore.exe
http://localhost is added to Local Intranet zone and Protected mode is disabled.
The issue is still happening.
Please advise

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment