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
Error trying to run grunt-lib-phantomjs on windows #59
Comments
Did you see any errors during install? |
Looked ok, npm install phantomjs:
npm install grunt-lib-jasmine
There's a warning about not being able to remove a temporary directory, but phantomjs ends up installed in the root of the project, and phantomjs.exe is present / runnable. |
Still not found a solution for this error. |
Will this Error help? Running PhantomJS...ERROR
|
Also hitting the same error...currently have PhantomJS 1.9.7 running. Running PhantomJS...ERROR
|
Also getting this issue. |
+1 |
1 similar comment
+1 |
Issue:
a) Fix phantomjs not found:
But now, when running:
I get (even though, grunt-lib-phantomjs is installed and found /node_modules):
|
I had this issue while trying to run tests with grunt-contrib-jasmine. The last thing I did to fix it was to remove and reinstall grunt-contrib-jasmine through npm. I suspect npm install does not work as well on Windows as Linux/Mac. Just a guess. :/ |
I also have this problem, any news? phantomjs is running OK from command prompt |
Hello, i've hit same issue as almost everyone here:
I've solved my case with simple re-building npm dependences. |
When in run jasmine using grunt i see the following message. But this generates specRunner html file.Im trying to get the test execution summary on command line. And it fails because of following message. Running "jasmine:unit" (jasmine) task Warning: Cannot read property 'pid' of undefined Use --force to continue. Aborted due to warnings. Versions:Phantomjsjs: 1.9.8 "grunt server --stack" logs:TypeError: Cannot read property 'pid' of undefined Aborted due to warnings. Please help me. What am I doing wrong here? Thanks! |
From all the stack traces above, I conclude that there is a problem with the path of A fresh install of this package should fix the issue. If persist, please report it to https://github.com/Medium/phantomjs. Closing this for now, feel free to ask if you have followup questions. |
The text was updated successfully, but these errors were encountered: