Bump chrome-for-testing to 130.0.6723.91 #3399
Draft
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
|
|
Recent Selenium builds have been failing with
WebDriverError: disconnected: not connected to DevTools
(failed to check if window was closed: disconnected: not connected to DevTools)
even though we haven't changed anything that I'm aware of. Trying to update our
Chrome dependencies here to see if that helps in any way.
Also bump selenium-webdriver to 4.26.0; I've combined it with this commit
because the changelog suggests it's somewhat tied to specific Chrome versions:
https://github.com/SeleniumHQ/selenium/blob/trunk/javascript/node/selenium-webdriver/CHANGES.md
mwiencek
force-pushed
the
chrome-for-testing-130
branch
from
63fdbf1
to
775be2b
Compare
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.
Problem
Recent Selenium builds have been failing with
even though we haven't changed anything that I'm aware of.
Solution
Trying to update our Chrome dependencies here to see if that helps in any way.
Also bump selenium-webdriver to 4.26.0; I've combined it with this commit because the changelog suggests it's somewhat tied to specific Chrome versions: https://github.com/SeleniumHQ/selenium/blob/trunk/javascript/node/selenium-webdriver/CHANGES.md
Testing
None yet, opening this to see if the build passes with these changes.