FIX Lock chrome and chromedriver to v126 until we know why 127 fails #140
Conversation
This file contains 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
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.
As per silverstripe/.github#287 (comment) the recent version of chromedriver seems to be causing problems in our behat that can't be reproduced directly by user interaction. I opened an issue about this with
php-webdriver/webdriverwhich seems to be what directly drives chromedriver. Hopefully they can resolve it from their end.In the meantime, this PR locks the version we use to the last version that is known to not have this problem.
I've opened #141 to revisit this in a month's time (or if the underlying issue is directly resolved)
Issue