[ci-scan] Recurring: NavEvents_ShellItemChanged tests time out on Windows in maui-pr-uitests

[github-actions]

Summary

NavEvents_ShellItemChanged_NavigatingEvent_SourceIsShellItemChanged (and related NavEvents_ShellItemChanged_* tests) intermittently time out waiting for a UI element during Shell item-changed navigation in the Windows UITests Controls Shell task.

Build Information

• Pipeline: maui-pr-uitests (definition 313)
• Build: 1491320
• Build ID: 1491320
• Branch: main
• First seen: 2026-06-27 (build 1484478)
• Occurrences: 2 in last 10 builds (1484478 on 2026-06-27, 1491320 on 2026-07-02)

Affected Legs

• Windows UITests — Controls Shell task (WinUI, Mono runtime, windows10, API 10.0.19041.0)

Error Message

Failed NavEvents_ShellItemChanged_NavigatingEvent_SourceIsShellItemChanged [18 s]
  Error Message:
   System.TimeoutException : Timed out waiting for element...
  Stack Trace:
     at UITest.Appium.HelperExtensions.Wait(...) in HelperExtensions.cs:line 2757
     at UITest.Appium.HelperExtensions.WaitForElement(...)  in HelperExtensions.cs:line 795
     at Microsoft.Maui.TestCases.Tests.ShellNavigationFeatureTests.NavigateToPage2() in ShellNavigationFeatureTests.cs:line 18
     at Microsoft.Maui.TestCases.Tests.ShellNavigationFeatureTests.NavEvents_ShellItemChanged_NavigatingEvent_SourceIsShellItemChanged() in ShellNavigationFeatureTests.cs:line 554

Recommended Action

1. Locate NavEvents_ShellItemChanged_NavigatingEvent_SourceIsShellItemChanged in src/Controls/tests/TestCases.Shared.Tests/Tests/FeatureMatrix/ShellNavigationFeatureTests.cs at line 554.
2. The test calls NavigateToPage2() which times out waiting for a UI element — this suggests the Shell ShellItemChanged navigation event handling on Windows may be slower than expected, or the navigation is not completing correctly.
3. Check src/Controls/src/Core/Shell/ShellNavigationManager.cs and the Windows-specific Shell handler (src/Controls/src/Core/Handlers/Shell/ShellHandler.Windows.cs) for any recent changes that could slow down ShellItem switching.
4. The failure on both build 1484478 and 1491320 (with a gap on 1486368 and 1489272 where the test may not have run or passed) suggests intermittent timing sensitivity. Consider adding a small wait or increasing the element-wait timeout specifically for Windows in NavigateToPage2().
5. Also check if the Mono runtime variant introduces additional overhead compared to CoreCLR for Shell navigation event firing on WinUI.

Generated by CI Failure Scanner ·

Generated by CI Failure Scanner · 460.4 AIC · ⌖ 11.5 AIC · ⊞ 8.6K · ◷

[PureWeen]

Closing this scanner issue as stale/non-reproducing after exact-test review. The affected NavEvents_ShellItemChanged test family passed across five complete main WinUI runs from 1533309 through 1544324, including first and duplicate-attempt evidence. No root-cause fix is claimed.

[PureWeen]

Reopening after two independent raw-log audits found an exact retry-masked recurrence in the closure window. Main UI build 1535911, WinUI Shell log 5215, records both tracked NavEvents_ShellItemChanged tests failing on the first attempt with the same NavigateToPage2 WaitForElement timeout, then passing only after the leg retry.