-
Notifications
You must be signed in to change notification settings - Fork 5k
[release/8.0-staging] [infra][apple-mobile] Migrate MacCatalyst and iOS/tvOS simulator jobs to osx.14.arm64.open
and osx.15.amd64.open
queues
#114633
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This reverts commit 8156e31.
Tagging subscribers to this area: @akoeplinger, @matouskozak |
osx.14.arm64.open
and osx.15.amd64.open
queuesosx.14.arm64.open
and osx.15.amd64.open
queues
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 9 out of 9 changed files in this pull request and generated no comments.
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-ioslikesimulator |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
0f54ae5
to
00b2d76
Compare
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
b01162f
to
25c85fe
Compare
I was trying to reproduce it locally but I'm hitting
when I execute it from xharness. However, when I do it manually from XCode it works, also when I execute the mlaunch commands manually it also works. I'm suspecting that maybe the simulator gets corrupted during the xharness launch process as we might not wait somewhere where we should. |
We already have several failing simulator runtime tests on rolling-builds https://dev.azure.com/dnceng-public/public/_build/results?buildId=1024193&view=results. Since we are already past of servicing cut-off for the last .NET 8 MAUI release, we don't need to maintain the simulator CI is green state. |
/ba-g acceptable regressions in simulator CI |
a3f72b1
into
dotnet:release/8.0-staging
Backport of #113313 to release/8.0-staging
Currently, we are using osx.1200.amd64.open and osx.1200.arm64.open for dotnet/runtime Apple simulator and MacCatalyst jobs. Since macOS 12 is after its EOL, we should migrate to queues with newer macOS version.
iOSSimulator, tvOSSimulator, MacCatalyst pipelines are migrated to:
osx.15.amd64.open
osx.14.arm64.open
(untilosx.15.arm64.open
has enough machines)Disabling failing tests against tracking issues.
Customer Impact
No impact, CI testing infra change
Regression
[If yes, specify when the regression was introduced. Provide the PR or commit if known.]
Testing
runtime-extra-platforms
Risk
Low: CI testing infra change