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. 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). Download and install Google Chrome Google Chrome is a fast web browser available at no charge. Interestingly, one of the solutions proposed to solve this is to use the gem that we just disabled How can we get this resolved Logs: /varlog/syslog: Jun 29 19:03 Logs: /varlog/syslog: Jun 29 19:03 talpa-deny google-chrome Ubuntu 14.04. 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. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |