-
Notifications
You must be signed in to change notification settings - Fork 35
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
URL for Chromedriver downloads changed in version >= 121 #104
Comments
We are seeing this too, but only since this afternoon. Up until this morning a fallback to an earlier build in the same major version was working:
But now we're getting the same results as @cbrews above.
Never mind, that fails for different reasons. Chrome 120 it is. |
Important to note that you might need something along the lines of this before installing chrome/chrome-driver: - run:
name: Apt update # I'm on debian, you might need to replace this...
command: sudo apt-get update |
Thank you @levicole and @cbrews, indeed this fixed the issue for us for now: steps:
- run:
# Remove this step once we unpin the chrome-version below
name: apt update for installing chrome
command: sudo apt-get update
- browser-tools/install-chrome:
chrome-version: "120.0.6099.224" # Wait until https://github.com/CircleCI-Public/browser-tools-orb/pull/105 is merged and fixes https://github.com/CircleCI-Public/browser-tools-orb/issues/104
- browser-tools/install-chromedriver |
Thanks @cbrews , we're being impacted by this as well but pinning the version is a good short-term fix as others have mentioned. |
Temporary workaround to fix tests for the time being. See CircleCI-Public/browser-tools-orb#104 for details.
Thank you for providing the workaround here, and the Pull Request. That's now been merged. |
Orb version
1.4.6
What happened
We started to receive this error when installing chromedriver as part of the browsertools orb:
I did some digging and found this commit correlated to the error, a change to the chrome-for-testing repo which is used for version resolution: GoogleChromeLabs/chrome-for-testing@3bfd77e
As of this commit it appears that chromedriver versions >= 121 have migrated from https://edgedl.me.gvt1.com/edgedl/chrome/chrome-for-testing to https://storage.googleapis.com/chrome-for-testing-public.
Current workaround is to pin version 120 (I'm on a debian machine):
Expected behavior
We should resolve the right version--but it looks like the place these are stored has changed. It also appears that this change is only affecting a subset of versions (121) so just changing the URL to resolve won't be enough, we need to conditionally select https://edgedl.me.gvt1.com/edgedl/chrome/chrome-for-testing for < 121 and https://storage.googleapis.com/chrome-for-testing-public for >= 121
The text was updated successfully, but these errors were encountered: