Summary
The iOS simulator monotouch test app intermittently launches but never connects to the XHarness test server. XHarness cancels the launch after three minutes and reports LaunchTimedOut after 15 minutes.
- Stable signature:
ios27-monotouch-harness-startup-timeout
- Classification: genuinely flaky test / simulator startup failure
- Distinct monitored PRs: 2
- Confirmed occurrences: 4
- First observed by the monitor: 2026-08-12 02:31 UTC
- Latest observed: 2026-08-12 05:09 UTC
Confirmed occurrences
Impact and investigation
The failing variation changes between attempts, while other variations in the same job pass. The app process is created successfully, but the test harness never receives a connection. This is not the NSUrlSession test hang and is not a deterministic product assertion failure.
Workaround
Rerun only the failed T: monotouch_ios job after confirming the PR is conflict-free and retry budgets permit it. Azure logs and artifacts are retention-limited.
Summary
The iOS simulator monotouch test app intermittently launches but never connects to the XHarness test server. XHarness cancels the launch after three minutes and reports
LaunchTimedOutafter 15 minutes.ios27-monotouch-harness-startup-timeoutConfirmed occurrences
266d164665536f387afbf8717eea43781e28fdaf, build 14944204Debug (PrepareAssemblies)inT: monotouch_ioslaunched the app but never established the harness connection.Debug (interpreter).Release (interpreter).1c46ed7045bad084f46a529392b8d6ccf1fdb64bT: monotouch_iosDebug (PrepareAssemblies)launchedcom.xamarin.monotouch-test, but the app never connected; XHarness loggedTest failed to start in 3 minutesand ultimatelyLaunchTimedOut.Impact and investigation
The failing variation changes between attempts, while other variations in the same job pass. The app process is created successfully, but the test harness never receives a connection. This is not the NSUrlSession test hang and is not a deterministic product assertion failure.
Workaround
Rerun only the failed
T: monotouch_iosjob after confirming the PR is conflict-free and retry budgets permit it. Azure logs and artifacts are retention-limited.