Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

RuntimeError when running jstests #3069

Closed
clone1018 opened this issue Jan 7, 2015 · 8 comments
Closed

RuntimeError when running jstests #3069

clone1018 opened this issue Jan 7, 2015 · 8 comments
Assignees
Labels

Comments

@clone1018
Copy link
Contributor

Running "webdriver:tests" (webdriver) task

RuntimeError: RuntimeError
     (UnknownError:13) An unknown server-side error occurred while processing the command.
     Problem: The path to the driver executable must be set by the phantomjs.binary.path capability/system property/PATH variable; for more information, see https://github.com/ariya/phantomjs/wiki. The latest version can be downloaded from http://phantomjs.org/download.html

     Callstack:
     -> init()

Makefile:70: recipe for target 'jstest' failed
make: *** [jstest] Error 8

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@techtonik
Copy link
Contributor

Can it be the failure reason for #3000 too?

@techtonik
Copy link
Contributor

Looks like we're hitting webdriverio/webdriverio#342

@techtonik
Copy link
Contributor

Travis doesn't fail, because it has phantomjs binary in PATH. http://docs.travis-ci.com/user/gui-and-headless-browsers/#Using-PhantomJS

@techtonik
Copy link
Contributor

Upgrading grunt-webdriver to 0.5.1 (selenium 0.4.4) didn't help.

@techtonik
Copy link
Contributor

@clone1018 I can't repeat this error on LXC/LXD setup with grunt-webdriver updated in #3490 Can you test if it is still actual? What configuration/system do you run this on?

@jiri-janousek
Copy link

I have same issue in Debian Jessie. Phantomjs is in $PATH location, but not found by webdriver. Any ideas?

fenryxo@charmeleon:~/dev/projects/gratipay/gratipay.com$ which phantomjs 
/home/fenryxo/dev/tools/phantomjs/bin/phantomjs
fenryxo@charmeleon:~/dev/projects/gratipay/gratipay.com$ phantomjs --version
1.9.8

@chadwhitacre
Copy link
Contributor

I think we should move to a different jstest infrastructure (#3684) and see if that fixes this.

@chadwhitacre
Copy link
Contributor

Closing now that #3684 is done.

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

No branches or pull requests

4 participants