You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both Controls.DeviceTests-packaged and Controls.DeviceTests-unpackaged consistently time out waiting for HybridWebView test results on Windows (windows.11.amd64.client.open) after exactly 480 seconds, causing the Run DeviceTests Windows job to fail.
Investigate HybridWebView device tests on Windows — the test runner is waiting 480 s for results that never arrive, suggesting either a HybridWebView startup hang or a WebView2 initialization failure on the Windows 11 Helix agents.
Check src/Controls/tests/DeviceTests/ under the HybridWebView category for Windows-specific initialization paths.
Summary
Both
Controls.DeviceTests-packagedandControls.DeviceTests-unpackagedconsistently time out waiting for HybridWebView test results on Windows (windows.11.amd64.client.open) after exactly 480 seconds, causing theRun DeviceTests Windowsjob to fail.Build Information
Affected Legs
Controls.DeviceTests-packaged— Windows 11 AMD64 (packaged app)Controls.DeviceTests-unpackaged— Windows 11 AMD64 (unpackaged app)windows.11.amd64.client.openError Message
Helix jobs:
1b3e1f78-5daf-4a45-9525-9e7f0d917531(latest build),b9f6d4b4-6bf2-4060-8eaa-2a497ffd55ca(prior build)Recommended Action
HybridWebViewdevice tests on Windows — the test runner is waiting 480 s for results that never arrive, suggesting either a HybridWebView startup hang or a WebView2 initialization failure on the Windows 11 Helix agents.src/Controls/tests/DeviceTests/under theHybridWebViewcategory for Windows-specific initialization paths.HybridWebViewHandlermembers on iOS are decorated with[RequiresUnreferencedCode], which may indicate related instability in the handler. Check if Windows path has analogous initialization issues.Controls.DeviceTestson Windows with the HybridWebView test category enabled.