Skip to content
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

chore: revert to Chrome 119.0.6045.105 #11540

Merged
merged 1 commit into from Dec 13, 2023
Merged

chore: revert to Chrome 119.0.6045.105 #11540

merged 1 commit into from Dec 13, 2023

Conversation

jrandolf
Copy link
Contributor

@jrandolf jrandolf commented Dec 13, 2023

Screenshot tests were flaky starting from 120.x.

Bisecting shows there is an issue with commits https://chromium.googlesource.com/chromium/src/+log/b8b95f5715b4bd2348e537b740048e4b6aa281b1..8026f46b0e73174f33834a26748107d1089a83bf however local builds cannot reproduce the flakiness from either ends of the commit range.

Testing this with 121.0.6167.8, the tests no longer flake so it's assumed there is a bug with the 120.x.

For now, we will revert back to the previous working version as a backmerge is unlikely. We will continue with the Chromium roll once Beta (121.0.6167.8) is stable.

@jrandolf jrandolf force-pushed the jrandolf/revert branch 9 times, most recently from 172a476 to a15ec9c Compare December 13, 2023 13:24
@jrandolf jrandolf changed the title fix: revert to Chrome 119.0.6045.105 chore: revert to Chrome 119.0.6045.105 Dec 13, 2023
@jrandolf jrandolf enabled auto-merge (squash) December 13, 2023 13:48
@jrandolf jrandolf merged commit 62a5a07 into main Dec 13, 2023
53 checks passed
@jrandolf jrandolf deleted the jrandolf/revert branch December 13, 2023 13:52
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.

None yet

2 participants