Commit d6e2a9d
[release/10.0] Fix flaky CanElevateEffectiveMaxItemCount_WhenOverscanExceedsMax (#67705)
Backport of #66291 to release/10.0.
The test was flaky because GetVisibleItemIndices() was called once and the
result was reused in all Browser.True() retry loops and across PageDown
iterations. In server mode, the async virtualization update had not finished
yet when the snapshot was taken, so the retry loops kept checking a stale list
that never reached 200 items.
Fix by re-querying GetVisibleItemIndices() inside each Browser.True() loop so
retries see the current DOM state.
This fix was already made on main via #66291 but was never backported to
release/10.0, where the test is still flaking in the components-e2e pipeline.
Co-authored-by: Ilona Tomkowicz <32700855+ilonatommy@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>1 parent 3d6aeb1 commit d6e2a9d
1 file changed
Lines changed: 15 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
578 | 578 | | |
579 | 579 | | |
580 | 580 | | |
581 | | - | |
582 | | - | |
583 | | - | |
| 581 | + | |
| 582 | + | |
| 583 | + | |
| 584 | + | |
| 585 | + | |
| 586 | + | |
| 587 | + | |
| 588 | + | |
584 | 589 | | |
585 | 590 | | |
586 | 591 | | |
| |||
595 | 600 | | |
596 | 601 | | |
597 | 602 | | |
598 | | - | |
599 | | - | |
| 603 | + | |
| 604 | + | |
| 605 | + | |
| 606 | + | |
| 607 | + | |
| 608 | + | |
| 609 | + | |
600 | 610 | | |
601 | 611 | | |
602 | 612 | | |
| |||
0 commit comments