Skip to content

[CI] iOS 27 monotouch-test stalls in NSUrlSession redirect tests with simulator daemon crash loops #26221

Description

@dalexsoto

Failure signature

monotouch-test starts executing MonoTests.System.Net.Http.MessageHandlerTest on the iOS 27 simulator, reaches the NSUrlSession credential/cross-origin redirect tests, then stops producing test output until xharness' 15-minute timeout. The same runs collect repeated intelligencetasksd crash reports and a SpringBoard crash report.

Representative last test activity:

MonoTests.System.Net.Http.MessageHandlerTest.NSUrlSessionHandlerCredentialsCrossOriginRedirectTarget

or immediately after:

[PASS] NSUrlSessionHandlerOriginCredentialCacheNotSentToCrossOriginRedirectTarget

Confirmed occurrences

PR / head Build and job Timed-out variations
#26200 / 966f7cc95666adf0926c09964990868e5f161864 14718622 - monotouch_ios Release (trimmable static registrar, NativeAOT) and Release (managed static registrar, all optimizations)
#26208 / 34b9f4d4972752561d6769b7f1ef0fbe276e049c 14718968 - monotouch_ios Release (NativeAOT, .NET 11 defaults)

First observed: 2026-07-21 15:25 UTC. Latest observed: 2026-07-21 17:36 UTC. Recurrence: 3 variations across 2 distinct monitored PRs.

Diagnosis and impact

This is classified as a genuinely flaky iOS 27 simulator/NSUrlSession failure:

  • The affected PRs modify unrelated framework bindings.
  • Other monotouch-test variations in the same jobs pass.
  • The failure is a silent stall rather than an assertion or product build error.
  • Repeated simulator-daemon crashes accompany each timeout.

The failure blocks the complete simulator-test stage. The current workaround is to rerun failed jobs after the build is terminal and retry/merge gates permit it. Test reports and crash artifacts have limited retention.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ci-failureThe issue only affects CIci-postmortemCI post-mortem analysis: flaky tests, infrastructure failures, shared regressionstestsAnything related to tests

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions