Internet Explorer process failed to be killed after test run

[Dacke]

I believe that this is functionality that is broken as a result of the update the Karma 0.12. I believe this because this used to work find in the previous version of Karma, but now fails to stop the iexplorer process upon completion of the tests.

I've set the captureTimeout to 5000[ms] and singleRun to true and it still will not exit the process.
{ browsers: ['PhantomJS', 'IE'], captureTimeout: 5000, singleRun: true } If I open another window and type "pskill iexplore" (using sysinternals tool) then karma exits normally and without error.

This is killing my continuous integration server (TeamCity) because it appears that the build has hung up and I have to stop it.

karma@0.12.0 karma-cli@0.0.4 karma-jasmine@0.1.5 karma-ie-launcher@0.1.2 karma-phantomjs-launcher@0.1.2

[theodorejb]

I'm having this same issue. The strange thing is that it only happens on our continuous integration server (Server 2008 R2), but not on our development machine (Server 2012 R2). Both environments are running IE 11 and the following dependencies:

• karma@0.12.0
• karma-cli@0.0.4
• karma-jasmine@0.2.2
• karma-ie-launcher@0.1.3
• karma-chrome-launcher@0.1.2
• karma-firefox-launcher@0.1.3
• karma-junit-reporter@0.2.1

[bitwiseman]

This may be related to https://github.com/karma-runner/karma/issues/429 . I believe I'm seeing the same thing on Kama@10.2. And I can repro it with IE10.

Are both machines 64bit?
Have you tried setting IE_BIN? Try both specifying the 32bit IE and then the 64bit IE to see if the behavior differs. Have you tried changing the "protected mode" setting?

[Dacke]

All my build machines are 64 bit machines. I've tried setting the IE_BIN which does not appear to make any difference because it doesn't launch the specified version of Internet Explorer anyhow. It keeps launching the 32 bit version out of the x86 folder. I've double checked, I'm not running the browsers in protected mode and I didn't change this setting between the time it was working and now.

Here is the screen shot of me setting (and checking) the IE_BIN before running the tests just to find that the iexplore.exe process did not exit even after timeout.

Here in task manager, you can still see the process running even after the tests are completed.

Hopefully this information helps you out.

[cthorne66]

Hi, We seem to be having the same problem with IE 10 and 11 after upgrading to new version of Karma. We are using Jenkins as our CI. All tests run successfully, but the CI doesn't seem to ever notice that the job is done.

[mseankelly]

I had the same issue. Resolved it by reverting to grunt-karma v0.6.2, which depends on karma v0.10.10. Reverting to grunt-karma v0.7.2 (which depends on karma v0.11.0) did NOT work.

Not an ideal resolution, but this information may point to the core issue.

[sylvain-hamel]

I think #15 with karma-runner/karma#973 should have fixed this problem. Can you please confirm?

[theodorejb]

I can confirm that it is working for me now with v0.1.4.

[bitwiseman]

@sylvain-hamel - Thanks!

[sylvain-hamel]

Thanks for getting back.

[orceN2k]

I still have this problem.

grunt-karma@0.8.3 karma@0.12.23 karma-jasmine@0.1.5 karma-ie-launcher@0.1.5

Tests on my local machine work, also on the server with my user. but if the test will be started by a jenkins the tests fail. anyone an ideas what's wrong?

[moattarwork]

I have the same issue with IE9