move to latest selenium image#258
Merged
mshriver merged 1 commit intoRedHatQE:masterfrom Aug 26, 2024
Merged
Conversation
This could go too far the opposite direction, but I'd rather see failures because of selenium updates than get a false sense of security from being on an older version. Consumers of widgetastic will want to be on the latest version of selenium
mshriver
force-pushed
the
update-ci-selenium
branch
from
857ddec to
c723b69
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This could go too far the opposite direction, but I'd rather see failures because of selenium updates than get a false sense of security from being on an older version.
Consumers of widgetastic will want to be on the latest version of selenium.
py3.12-chrome is failing on main branch, pulling the pause:3.5 image fails with 404. The image definitely exists