-
Notifications
You must be signed in to change notification settings - Fork 253
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
Unhandled error event #35
Comments
Hi Sieben, I'll take a look at this as soon as I get a chance. Out of curiosity, do you get this error if you run |
Not at all. 2013/11/19 Rowan Manning notifications@github.com
|
@sieben Do you have the PhantomJS binary in your I think this issue comes from the shim.js file in the phantomjs-node module used. If you don't have the binary in your |
Yeah now it works. But I'm very surprised that it works in .travis.yml without mentionning Phantom. |
Glad you got it working, I'll see if I can make that error message a bit more descriptive. PhantomJS isn't in the travis config because we currently only run the unit tests on travis, where the PhantomJS stuff is mocked |
Fixes the broken badges in our README
sieben@sieben-lincs:~|⇒ pa11y nature.com
Welcome to Pa11y
We'll sniff your page for you now.
events.js:72
throw er; // Unhandled 'error' event
^
Error: spawn ENOENT
at errnoException (child_process.js:980:11)
at Process.ChildProcess._handle.onexit (child_process.js:771:34)
The text was updated successfully, but these errors were encountered: