Skip to content

[ci-fix-net11] De-flake AbsoluteLayout tests: wait for destination readiness (refs #36397) - #37365

Draft
github-actions[bot] wants to merge 1 commit into
net11.0from
ci-fix/issue-36397-cff29a71bb36ab46
Draft

[ci-fix-net11] De-flake AbsoluteLayout tests: wait for destination readiness (refs #36397)#37365
github-actions[bot] wants to merge 1 commit into
net11.0from
ci-fix/issue-36397-cff29a71bb36ab46

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Note

Are you waiting for the changes in this PR to be merged?
It would be very helpful if you could test the resulting artifacts from this PR and let us know in a comment if this change resolves your issue. Thank you!

Target branch: net11.0
Refs: #36397
Attempt: 1/10

Failure

The Windows Layout UI-test leg intermittently leaves all 18 VerifyAbsoluteLayout_* tests in OneTimeSetUp, timing out while waiting for the gallery's Go To Test button to disappear. The same Layout job succeeds in newer runs, classifying this as a test-quality flake rather than a deterministic product regression.

Change

Allow gallery fixtures to name an element that proves their destination page is ready. AbsoluteLayout now waits for its Options control after tapping Go To Test instead of using disappearance of a source-page button as a proxy for completed navigation. Existing gallery fixtures retain their current behavior.

Validation

Not run locally: the Windows Appium UI-test rig is unavailable on this Linux runner. The change preserves every test and assertion and replaces only the AbsoluteLayout setup synchronization point.

Previous approaches

Attempt Files Approach
1/10 UtilExtensions.cs, _GalleryUITest.cs, AbsoluteLayoutFeatureTests.cs Wait for an AbsoluteLayout destination control rather than source-button disappearance.

Generated by CI Failure Fixer (net11.0) · gpt56 · 633.4 AIC · ⌖ 34 AIC · ⊞ 31K ·

…1/10)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).
There may be pipelines that require an authorized user to comment /azp run to run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants