-
Notifications
You must be signed in to change notification settings - Fork 30
Issue in running grover on windows #21
Comments
Tried to launch 'grover' through yogi but still didn't work. Below are the console error messages. @davglass, would be great if you can help me out with this issue and also point me to a resource who is supporting yui tools now.
|
Can you please post the contents of |
As for the 2nd issue, it looks like you don't' have yuidoc or selleck installed. While those should be installed as dependencies (assuming you ran |
Thanks @derek for looking into this. For some reasons, I can't share you the I have tried to update
Did you come across above issue ? Below are my selleck & yuidoc versions installed on my machine. Looks like the issue is nothing to do with them. Selleck 0.1.18 |
I think I might be seeing the same problem. I suspect your test uses relative paths to refer to the YUI seed file (as mine does). If you run grover directly on the test, it resolves the relative path with the file system happily. But yogi looks like it runs grover within the context of its server which imposes a root reference that your relative path can't step outside of. So the grover test fails as it can't resolve the reference to the YUI seed file. |
Just looking at this - https://github.com/yui/yui3-gallery/blob/master/src/gallery-datasource-async-function/tests/unit/test.html I see - Does this mean these unit tests are not runnable from the file system (ie double click the test and away she goes). Is that the model - that these then need to be always run from yogi? |
I think I am having a similar issue. Any ideas? $ grover index.html
Starting Grover on 1 files with [email protected]
Running 15 concurrent tests at a time.
events.js:85
throw er; // Unhandled 'error' event
^
Error: spawn phantomjs ENOENT
at exports._errnoException (util.js:746:11)
at Process.ChildProcess._handle.onexit (child_process.js:1046:32)
at child_process.js:1137:20
at process._tickCallback (node.js:355:11) |
I'm running into the same issue when trying to setup grover on a new machine. appreciate any inputs if anyone got to fix it. |
When I try to run grover on my module, it throws below error.
Appreciate any inputs to get this resolved.
The text was updated successfully, but these errors were encountered: