-
-
Notifications
You must be signed in to change notification settings - Fork 925
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
Can't run Chrome webdriver #3170
Comments
Just to be clear, you were able to verify this works with MRI? The reason I ask is chromedriver requires a separate download and installation. The selenium-webdriver gem then uses this downloaded binary. |
Yes, it works with MRI. This is a Rails 4.2 / Ruby 2.2.2 project that I'm trying to run with JRuby 9.0.0.0 |
I'm running into a similar issue with JRuby v9.0.0.0 final. No Capybara, but direct use of selenium-webdriver v2.46.2. Works fine with Rubinius v2.5.7. |
@pmontrasio @clonezone would either of you have a simple reproduction case that we could use to verify a fix for this? My experience with Capybara/Selenium is about three years old at this point, but I have a hunch that this might have to do with process spawning |
require 'selenium-webdriver'
webdriver = Selenium::WebDriver.for :chrome
webdriver.quit On Ubuntu v14.04.2 LTS, with Chrome v40, Chromedriver v2.10.267518, selenium-webdriver v2.46.2, and Rubinius v2.5.7, this works: the browser gets launched and shuts down. (You need to have Chrome and Chromedriver in your With everything else the same, switching to JRuby v9.0.0.0 results in
Note that the browser does launch with JRuby; it’s communication with the browser process that's the issue. |
@clonezone I am facing the same error currently in PFB the log generated. https://api.travis-ci.org/jobs/201592573/log.txt?deansi=true |
I still have no solution.
|
@clonezone: Okay! It was the issue with 2.7 version of chrome driver. I downgraded to 2.27, it works now. Thanks |
I have encountered the same issue, but downgrading the chrome driver to 2.27 did not resolve it. |
@venu14feb What is the error you are getting, can you please paste the logs |
@reach2jeyan, I am getting the below error: |
This appears to be working fine on JRuby master on my system...
|
As near as I can tell, the chromedriver installed on my Fedora appears to be in the 2.29 range, since it's for Chrome 57. All I did was @venu14feb Can you give more details about your environment? |
@headius, I am trying to run the cucumber scripts and using Ruby.
(The issue started after upgrading my machine to Windows 10. It asked to upgrade Ruby that supports 64 bit and I did) May I know what 'dnf install chromedriver' does? May be I couldn't find this command as I am using Ruby and not JRuby. |
Well, we can't help with C Ruby issues. If you are having the trouble with a current JRuby release, let us know. |
@venu14feb If you are using ruby, could you please place the chromedriver in the lib file of the ruby and check? |
@headius .. Sorry if this was the wrong post. @reach2jeyan .. Yes I did place the chromedriver.exe file in the bin folder and the same was defined in the path to be launched. Seems like the issue is to do with Windows 10 being 64 bit. |
@reach2jeyan ... The issue is, can't run the cucumber scripts from command prompt on windows 10 (which was fine on windows 7). Don't know why. But I found a solution, I installed the rubymine IDE and its running the scripts successfully now. |
@venu14feb Strange...! How could an IDE resolve the issue of chromedriver? |
Hi all can anyone help me to resolve the issue |
@sidh12 Unfortunately JRuby 1.7.x is not supported anymore. The error you get here appears to be trying to pass a nil value as DNS host when doing a lookup, but I don't know much more. If you stop by IRC or Gitter we may be able to help, but updating to JRuby 9.x is almost certainly your best path forward. |
This is the error I get when running Selenium with chrome
The driver has been set up with
This could be a bug of the Chrome webdriver not supporting JRuby but I'm starting from here because it could be caused by some peculiarity of the Java environment.
The text was updated successfully, but these errors were encountered: