Skip to content
This repository has been archived by the owner on Sep 7, 2022. It is now read-only.

fix: karma doesn't kill PhantomJS on windows when using singleRun:true #29

Merged
merged 1 commit into from
Apr 1, 2014

Conversation

sylvain-hamel
Copy link
Contributor

Now returns the node.exe process that runs phantom instead of the phantomjs.cmd process
Closes #27

@kasperp
Copy link

kasperp commented Mar 31, 2014

I hit #27 on Windows 8.1, x64, this solves the issue for me 👍

var isWin = /^win/.test(process.platform);
if (isWin) {
flags = flags.concat(win32PhantomJSPath(), captureFile);
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

little style thing:

} else {

please

@dignifiedquire
Copy link
Member

Some small styling issues other than that lgtm.

@sylvain-hamel sylvain-hamel self-assigned this Mar 31, 2014
Now returns the node.exe process that runs phantom instead of the phantomjs.cmd process
Closes karma-runner#27
@sylvain-hamel
Copy link
Contributor Author

@dignifiedquire ok now?

@dignifiedquire
Copy link
Member

👍

sylvain-hamel added a commit that referenced this pull request Apr 1, 2014
fix: karma doesn't kill PhantomJS on windows when using singleRun:true
@sylvain-hamel sylvain-hamel merged commit 5670fc5 into karma-runner:master Apr 1, 2014
@sylvain-hamel sylvain-hamel deleted the fix-27 branch April 19, 2014 03:49
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

PhantomJS was not killed in 2000 ms, sending SIGKILL
3 participants