Summary
The Controls Tests Helix work item on MacCatalyst (Mono runtime) consistently times out: XHarness kills the process after the 1-hour timeout with exit code 70 (TIMED_OUT). No crash is reported — the app launches but never finishes running all tests.
Build Information
- Pipeline: maui-pr-devicetests (def 314)
- Build: 1455984, 1455596
- Branch: net11.0
- First seen: build 1455596 (2026-06-09)
- Occurrences: 2 in last 2 builds (1455596, 1455984)
Affected Legs
DeviceTestsMacCatalyst (Windows) — Helix queue osx.26.arm64.open, Mono runtime
- Work item:
Controls Tests (exit code 70 = TIMED_OUT)
Error Message
[XHarness] apple test --target maccatalyst --timeout 01:00:00 --launch-timeout 00:06:00 ...
[09:27:42] dbug: Process 23890 didn't exit within 01:00:00 and will be killed
[09:27:44] dbug: 23890 Execution timed out after 3600 seconds and the process was killed.
[09:27:44] dbug: No crash reports, waiting 5 seconds for the crash report service...
XHarness exit code: 70 (TIMED_OUT)
Helix job: edfa0655-daae-4051-b831-2b327a36669e (build 1455596)
Recommended Action
- Fetch the full XHarness output log from the Helix console to find the last test that ran before the timeout — this identifies the test that is stuck.
- Investigate whether a specific test in
Controls.DeviceTests (Mono, MacCatalyst) has an infinite loop, deadlock, or hanging await on a UI thread.
- Compare with the CoreCLR variant (
DeviceTestsMacCatalyst_CoreCLR) — if CoreCLR passes, the issue may be Mono-specific dispatch or threading.
- Check
src/Controls/tests/DeviceTests/ for recent changes to controls that run long test suites on macOS.
Note: This is distinct from issue #103 (MacCatalyst CoreCLR osx.15.arm64.maui.open queue stall) — this failure is on Mono runtime on osx.26.arm64.open and is a process timeout, not a queue availability issue.
Area: src/Controls/tests/DeviceTests/ (MacCatalyst/Mono), eng/helix_xharness.proj
Generated by CI Failure Scanner (net11.0) · ● 100.2M · ◷
Summary
The
Controls TestsHelix work item on MacCatalyst (Mono runtime) consistently times out: XHarness kills the process after the 1-hour timeout with exit code 70 (TIMED_OUT). No crash is reported — the app launches but never finishes running all tests.Build Information
Affected Legs
DeviceTestsMacCatalyst (Windows)— Helix queueosx.26.arm64.open, Mono runtimeControls Tests(exit code 70 =TIMED_OUT)Error Message
Helix job:
edfa0655-daae-4051-b831-2b327a36669e(build 1455596)Recommended Action
Controls.DeviceTests(Mono, MacCatalyst) has an infinite loop, deadlock, or hanging await on a UI thread.DeviceTestsMacCatalyst_CoreCLR) — if CoreCLR passes, the issue may be Mono-specific dispatch or threading.src/Controls/tests/DeviceTests/for recent changes to controls that run long test suites on macOS.Note: This is distinct from issue #103 (MacCatalyst CoreCLR
osx.15.arm64.maui.openqueue stall) — this failure is on Mono runtime onosx.26.arm64.openand is a process timeout, not a queue availability issue.Area:
src/Controls/tests/DeviceTests/(MacCatalyst/Mono),eng/helix_xharness.proj