Summary

Controls.DeviceTests on Windows 11 (both packaged and unpackaged variants) fail with a 480-second timeout waiting for HybridWebView test results. The work items Controls.DeviceTests-packaged and Controls.DeviceTests-unpackaged exit with code 1 and the log shows [FAIL] Timeout waiting for HybridWebView test results after 480 seconds.

Build Information

• Pipeline: maui-pr-devicetests (definition 314)
• Build: 1446887
• Branch: main
• First seen: 2026-06-03
• Occurrences: 1 confirmed in this specific form (HybridWebView timeout in Controls.DeviceTests on windows.11.amd64.client.open)

Affected Legs

• Windows 11 AMD64 — DeviceTestsWindows (Windows) / Helix job 28431e8b-f62f-4d93-84b5-f2f72d3c108e
• Both packaged (Controls.DeviceTests-packaged) and unpackaged (Controls.DeviceTests-unpackaged)

Error Message

[FAIL] Timeout waiting for HybridWebView test results after 480 seconds

From:

• Controls.DeviceTests-packaged: ExitCode 1
• Controls.DeviceTests-unpackaged: ExitCode 1

Recommended Action

Investigate the HybridWebView device tests in src/Controls/tests/DeviceTests/ for Windows. The test runner hangs for 480 seconds before giving up — possible causes include:

1. HybridWebView not rendering or initializing on the Windows 11 Helix machine,
2. A JavaScript bridge message that is never received,
3. A deadlock in the test's async wait logic.
   Check if a recent change to HybridWebView on Windows (in src/Core/src/Handlers/HybridWebView/) introduced a regression that blocks the test completion signal.

Generated by CI Failure Scanner · ● 68.4M · ◷