[mobile] Switch iOS device test legs in runtime.yml to simulators#128763
Open
kotlarmilos wants to merge 1 commit into
Open
[mobile] Switch iOS device test legs in runtime.yml to simulators#128763kotlarmilos wants to merge 1 commit into
kotlarmilos wants to merge 1 commit into
Conversation
The three ios_arm64 (device) library-test legs in runtime.yml currently target the osx.15.amd64.iphone.open Helix queue, which is failing to enumerate devices (issue dotnet#125135). Temporarily switch the Mono Full-AOT smoke, NativeAOT smoke, and CoreCLR smoke legs from ios_arm64 to iossimulator_arm64 so the main runtime pipeline keeps producing iOS test signal while the device queue is being fixed. Build args are left intact so the change is trivial to revert. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
kotlarmilos
changed the title
Contributor
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the main runtime.yml pipeline to keep iOS test coverage flowing by switching three iOS device smoke-test legs over to the corresponding iOS simulator (arm64) platform, avoiding reliance on the device Helix queue.
Changes:
- Switched the Mono Full-AOT + AggressiveTrimming smoke leg from
ios_arm64toiossimulator_arm64. - Switched the NativeAOT smoke leg from
ios_arm64toiossimulator_arm64. - Switched the CoreCLR smoke leg from
ios_arm64toiossimulator_arm64, and updated nearby comments to document the temporary workaround.
Show a summary per file
| File | Description |
|---|---|
| eng/pipelines/runtime.yml | Re-targets three iOS library-test legs from device (ios_arm64) to simulator (iossimulator_arm64) and documents the reason inline. |
Copilot's findings
- Files reviewed: 1/1 changed files
- Comments generated: 0
matouskozak
approved these changes
May 29, 2026
Member
matouskozak
left a comment
matouskozak
left a comment
There was a problem hiding this comment.
Thank you for switching the configs. I wonder if we could try restarting the apple tv via cmd line in xharness to potentially prevent these in the future. I'll take a look if it's possible but any suggestions are welcomed.
This was referenced May 29, 2026
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Due to infrastructure issues with the
osx.15.amd64.iphone.openHelix device queue #123796, switching theios_arm64library-test legs ineng/pipelines/runtime.ymltoiossimulator_arm64.