Pin Chrome 127 in Jasmine CI tests #7128
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
birkskyum
changed the title
|
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is a regression in Chrome 128, this pins chrome 127.0.6533.119 in CI.
Closes #7126
jasminetests start failing with Chrome 128 onmasterand other branches #7126