I’d like to figure out the ChromeDriver connection problem, possibly by understanding how/why it worked with the gem, but I might use a patched version of the gem that allows pinning the ChromeDriver version to 2.27 as a quick workaround. Beginner: How to Install Google Chrome in Ubuntu 14.04 If you’ve tried to install Google Chrome in Ubuntu Linux, you may have noticed that it’s not available in the Ubuntu Software Center. The first of his guides starts from the ground up, using Ubuntu server and a handful of packages to create a lightweight combination of X and Openbox running Chrome on boot. This could work if chromedriver-helper allowed to configure the ChromeDriver version to install, but it’s not currently the case (there is an open pull-request for this on GitHub). Linux developer Oli Warner recently published a pair of articles that walk through the creation of single purpose setups using Ubuntu 14.04 LTS and Google Chrome. Interestingly, one of the solutions proposed to solve this is to use the gem that we just disabled I guess that some files created by the gem and kept in the cache were interfering even after the gem was disabled.Ī quick search on the forums led me to a topic discussing a similar issue. Unable to connect to chromedriver 127.0.0.1:9515ĮDIT: we fixed this by rebuilding without cache. Les ordinateurs Chromebook fonctionnent nativement avec le système dexploitation Chrome OS, de Google. This does succeed at preventing the installation of the problematic newer version of ChromeDriver, but we have now another problem: Selenium WebDriver fails to connect to ChromeDriver, with this error message: Selenium::WebDriver::Error::WebDriverError: Gem "chromedriver-helper" unless ENV.key?('CIRCLECI') We could override the default command, but our next try has been this: group :test do
This doesn’t work as is, because the default dependencies command(1) doesn’t exclude the development group.
I haven’t tried to fix it yet, but I think that simply moving the gem to the :development group should be a good enough solution.
0 kommentar(er)
