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.

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.

Chromedriver ubuntu