Further attempt to fix CancelsOutdatedRefreshes_Async in CI #32998
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.
The previous attempt to fix this in #32869 actually made it worse. It went from being flaky in CI to failing 100% of the time in CI, even though it passes 100% of the time locally.
The implementation here is just a manual equivalent to the
behavior: 'smooth'
flag to see if that works better.Sidenote: I'm increasingly thinking it may be a more fundamental aspect of the CI environment that makes anything based on human timescales for interactivity (which UI tests should and must be) unviable. Browsers aren't designed to operate in conditions where they're unable to execute code in response to events because of excessive resource contention. If that is the case we're going to have to set up a separate, dedicated environment for running E2E tests that is not in contention for resources with other build or test activities, or at least have a more sophisticated mechanism for retries. If the Playwright efforts prove this wrong then of course that would be better still, but as yet we haven't got there.