镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

[Test][NO-MERGE] Scout iOS simulator and MacCatalyst in runtime CI - #134859

Closed
matouskozak wants to merge 1 commit into
dotnet:mainfrom
matouskozak:matouskozak-simulator-and-catalyst-scouting
Closed

matouskozak wants to merge 1 commit into
dotnet:mainfrom
matouskozak:matouskozak-simulator-and-catalyst-scouting

Conversation

@matouskozak

@matouskozak matouskozak commented Sep 29, 2026 •

Copy link
Copy Markdown
Member

Testing only — DO NOT MERGE. Separate from #133575, which remains unchanged. Started from main at 032786e1c2ef, including the CoreCLR managed-argument fix from #134767.

Matrix

Eight Release / arm64 / non-smoke configurations: each target runs CoreCLR and NativeAOT, each with runtime and library suites. Runtime tests use innerloop/Priority0; library submission uses TestScope=innerloop.

Target Helix queue
iOS simulator osx.amd64.iphone.scouting.open
MacCatalyst osx.amd64.appletv.scouting.open

The queues select hosts, not device targets. Existing templates produce ios-simulator-64 and maccatalyst runners without device deployment/signing commands; Catalyst uses ad-hoc app signing. Observed workers are Apple M1/Arm64 despite their legacy queue names.

Moves this matrix into automatic runtime PR CI and skips unrelated public pipeline stages; disables VMR PR triggering. Retains internal queue selection and secure variable-group guards. No physical iOS/tvOS jobs, Mono, Debug/Checked, AppSandbox, smoke-only, outerloop/Priority1, or TestScope=all.

Includes the necessary Apple test-host integration: scene-based startup once per process, app-build deployment target 15.0 (not a .NET minimum-support policy change), and xUnit-only NativeAOT library-runner injection. Shared runtime native linking/packaging and #134767 remain intact. No new quarantines.

Validation and limits

  • Scoped local YAML evaluation followed all eight configurations through existing queue/submission templates; checked internal queue preservation and unrelated-public-pipeline gating. Actual MSBuild evaluations checked project discovery, Priority0, runner selection and empty device-signing commands. Azure server-side preview was unavailable without authentication. After PR creation, the actual automatic runtime build 1616184 generated exactly the intended eight jobs plus one Helix monitor; its results are still pending.
  • AppleAppBuilder and the iOS-simulator NativeAOT product baseline built successfully. The runner-guard regression failed against the original targets; all eight fixed MSBuild assertion cases passed.
  • Ten native startup probes built/launched both UI templates across local iOS 26.5 simulator and MacCatalyst, including startup-once checks. These used runtime stubs, not managed tests.
  • The real NativeAOT Exceptions runner built with CI packaging settings, its Helix proxy produced a simulator app, and local iOS 26.5 execution reported 2 executed, 1 passed, 1 failed. UnwindFpBleedTest returned 1 instead of 100. This matches the observed device failure signature, not a proven shared cause; it remains visible and unquarantined. Proxy app build also emitted the existing BaseIntermediateOutputPath warning (MSB3539).

This is not full-suite signoff. Local validation used Xcode 26.6; iOS 27 simulator availability on the scouting pool is unverified. Observed scouting hosts ran macOS 26.5, so this does not establish MacCatalyst coverage on macOS 27. No CI reruns/cancellations or new recurring monitoring were requested or performed.

Note

This PR and its description were generated with GitHub Copilot.

Run Release CoreCLR and NativeAOT runtime/library innerloops on the Apple scouting host pools. Disable unrelated public pipeline stages for this NO-MERGE testing branch and preserve current-main runtime argument handling.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@matouskozak matouskozak added the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label Sep 29, 2026
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 5 pipeline(s).
11 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

@dotnet-policy-service

Copy link
Copy Markdown
Contributor

Tagging subscribers to this area: @akoeplinger, @matouskozak, @simonrozsival
See info in area-owners.md if you want to be subscribed.

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

Labels

area-Infrastructure-mono NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant