-
Notifications
You must be signed in to change notification settings - Fork 34
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
install-chromedriver command puts 'chromedriver' binary at unexpected location for Chrome 115 #81
Comments
…ic#81) In previous chromedriver releases, the ZIP archives would contain the 'chromedriver' binary in the root directory of the archive. This file was then moved to the target directory, typically /usr/local/bin/chromedriver With chromedriver 15 however, the ZIP archives contain a new platform-specific subdirectory. Thus, the actual binary is at e.g. 'chromedriver-linux64/chromedriver'. As it is, the 'chromedriver-linux64' directory is renamed to 'chromedriver' and *that* is then moved to the target directory. This results in the final executable to end up at /usr/local/bin/chromedriver/chromedriver This is not backwards compatible with usages of the orb expecting the previous location (e.g. because they expect that 'install-chromedriver' puts the binary into a directory which is part of the PATH).
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?
|
Yeah, Failing for us too - now instead of failing fast during chromedriver install it just fails later during the test runs with:
or
|
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:
The text was updated successfully, but these errors were encountered: