Closed birkskyum closed 2 months ago
The following packages have unmet dependencies:
google-chrome-stable :
How about using older versions of Chrome or CI containers?
I think it actually doesn't solve the problem much, it just hides... people will get v128 on their machines, quite fast, so if it breaks there, these tests have to be fixed, or noCI-flagged. If the CI hadn't used "latest" we wouldn't know about this issue.
Let me also ask @antoinerg to look at this CircleCI problem.
There is a regression in Chrome 128, this pins chrome 127.0.6533.119 in CI.
Closes #7126
7126