Skip to content
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

PhantomJS Error Message #55

Closed
andyl opened this issue Apr 21, 2013 · 3 comments
Closed

PhantomJS Error Message #55

andyl opened this issue Apr 21, 2013 · 3 comments

Comments

@andyl
Copy link

andyl commented Apr 21, 2013

Teabag is running specs from the command line - yea! But I get a funky error message "No such file or directory..."

Starting the Teabag server... 
Teabag running default suite at http://127.0.0.1:42806/teabag/default
./bin/rake: No such file or directory - phantomjs --version
./bin/rake: No such file or directory - phantomjs --version
.
Finished in 0.00500 seconds
1 example, 0 failures

Any ideas re: how to suppress/eliminate this message?

I'm running: Ubuntu 12.04 32-bit, teabag 0.7.1, ruby 1.9.3p327perf, rails 3.2.13.

I tried:

  • gem 'phantomjs-linux' #=> made no difference
  • apt-get install phantomjs #=> broke teabag, even when setting PHANTOMJS_BIN
@jejacks0n
Copy link
Owner

Ah, so it's looking for phantomjs, using a sort of "which" type of functionality.. I expect the error is coming from this, but I'm not sure: https://github.com/modeset/teabag/blob/master/lib/teabag/utility.rb

Is phantomjs in your path?

@andyl
Copy link
Author

andyl commented Apr 21, 2013

OK so - the phantomjs from the apt-get repo was at version 1.4. I downloaded the newest phantomJS (version 1.9), installed it on my path, and everything looks great.

I added a little blurb to the wiki page in case someone else runs into this issue.

Thanks very much for Teabag - excited to try this on my project!

@andyl andyl closed this as completed Apr 21, 2013
@jejacks0n
Copy link
Owner

Awesome, thank you!

As an aside, I have a javascript project called Mercury Editor, and the level of questions/support needs between people writing specs for their projects vs. people wanting to use a javascript library is considerably different. It's really rewarding to support a project for folks that read documentation and are able to clarify issues. Cheers! =)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants