Skip to content

[chore] CI maintenance: Fix error where Chrome fails to download#7711

Open
emilykl wants to merge 6 commits intomasterfrom
upgrade-circleci-browser-tools-version-ci
Open

[chore] CI maintenance: Fix error where Chrome fails to download#7711
emilykl wants to merge 6 commits intomasterfrom
upgrade-circleci-browser-tools-version-ci

Conversation

@emilykl
Copy link
Contributor

@emilykl emilykl commented Feb 17, 2026

Fixes the error currently seen in the CI on main, where Chrome fails to install due to a 404 error:

W: https://download.docker.com/linux/ubuntu/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_132.0.6834.110-1_amd64.deb:
2026-02-04 04:45:27 ERROR 404: Not Found.
/bin/bash: line 185: google-chrome-stable: command not found
/bin/bash: line 187: google-chrome-stable: command not found
Google Chrome v132.0.6834.110 (stable) failed to install.

It seems this error is because the URL used by the Debian package index to download Chrome returns a 404, possibly because the Chrome version is too old (~1 year).

This PR:

  • Bumps the Chrome version up to Chrome 133, which fixes the 404
  • Upgrades the CircleCI browser-tools orb from 1.5.1 to 2.4.0 for good measure (some name changes for arguments required as part of this change, replacing hyphens with underscores)
  • Updates one map baseline image whose satellite image tiles have changed
  • Slightly changes the expected path in one geo test to fix failure (the change in the path is miniscule and not visible to the eye)
  • Massages one flaky transitions test to get it to pass more reliably

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant