Block test that is failing after switching to latest-chrome #61881
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
DeagleGross
approved these changes
May 12, 2025
wtgodbe
approved these changes
May 12, 2025
3 tasks
|
Is there chromium issue for the change/bug ? |
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.
Description
Block the non-enhanced navigation test. Currently we rely on "https://dl.google.com/chrome/install/latest/chrome_installer.exe" for Selenium tests on Windows. For a few weeks, we can see stable failures on
CanUseFormWithMethodGetthat uses non-JS navigation. When running with an older chrome, e.g. "http://dl.google.com/chrome/install/375.126/chrome_installer.exe" that was used on the CI 6 weeks ago, this test never fails.The failure is connected with a change in how the browser handles navigation and can be unblocked once it's fixed on a new browser version.
Fixes #61880