Closed frerich closed 1 year ago
Can confirm, this is current an issue for a large number of folks. https://googlechromelabs.github.io/chrome-for-testing/
Can I assume this address this error? None of the workarounds from the previous PR seem to work for me.
Installed version of Google Chrome is 115.0.5790.98 115.0.5790.98 will be installed mv: cannot move 'chromedriver' to '/usr/local/bin/chromedriver': File exists
Yeah, Failing for us too - now instead of failing fast during chromedriver install it just fails later during the test runs with:
Webdrivers::VersionError:
Unable to find latest point release version for 115.0.5790. You appear to be using a non-production version of Chrome. Please set `Webdrivers::Chromedriver.required_version = <desired driver version>` to a known chromedriver version: https://chromedriver.storage.googleapis.com/index.htm
or
Webdrivers::NetworkError:
# Net::HTTPServerException: 404 "Not Found" with https://chromedriver.storage.googleapis.com/LATEST_RELEASE_115.0.5790
# /home/circleci/project/bundle/ruby/3.1.0/gems/webdrivers-5.2.0/lib/webdrivers/network.rb:19:in `get'
Hi @frerich this should be fixed in the newly published orb version 1.4.3
I can confirm - version 1.4.3 works as expected. Thanks!
Orb version
1.4.2
What happened
CI builds expecting that the
install-chromedriver
commands puts a binary at/usr/local/bin/chromedriver
started failing. This only appeared with Chrome 115. These days, the binary appears to end up in/usr/local/bin/chromedriver/chromedriver
.Expected behavior
The
chromedriver
binary should always end up in the directory specified by theinstall-dir
option. By default, this would be/usr/local/bin
. Thus, after successful execution of theinstal-chromedriver
command, there should be a binary/usr/local/bin/chromedriver
.Further observations
It appears that the structure of chromedriver ZIP files changed slightly: with Chromedriver 114 I get
but with chromedriver 115 there's an extra 'chromedriver' subdirectory: