Uh oh!
There was an error while loading. Please reload this page.
[mono] Run full mobile library tests - #132887
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 972fe987-edc4-4e1f-a9e7-18da51c0ee18
|
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. |
matouskozak
commented
Aug 28, 2026
/azp run runtime-extra-platforms |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
Tagging subscribers to this area: @akoeplinger, @matouskozak, @simonrozsival |
There was a problem hiding this comment.
Pull request overview
This PR updates the runtime extra-platforms Azure Pipelines definitions to run the full Mono libraries test suite (instead of smoke subsets) on key mobile legs, increasing test coverage on iOS simulator (arm64 interpreter) and Android arm64 devices.
Changes:
- iOS simulator (arm64, Mono interpreter): switch from forcing
/p:RunSmokeTestsOnly=trueto using$(_runSmokeTestsOnlyArg)(which evaluates to full-suite on these pipelines) and update the header comment accordingly. - Android devices (arm64, Mono): add a new
platform-matrixjob to run Mono libraries tests onandroid_arm64, using the same smoke/full toggle mechanism.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| eng/pipelines/extra-platforms/runtime-extra-platforms-ioslikesimulator.yml | Removes the hardcoded smoke-only flag for the Mono iOS simulator interpreter leg so it runs the full libraries tests suite. |
| eng/pipelines/extra-platforms/runtime-extra-platforms-android.yml | Adds a new Mono Android arm64 devices job to run the full libraries test suite on runtime-extra-platforms/runtime-android. |
matouskozak
commented
Aug 31, 2026
/azp run runtime-extra-platforms |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
jkotas
commented
Aug 31, 2026
What's the point of adding more Mono test coverage in main (.NET 12)? I would expect us doing the opposite. |
The goal is to gain coverage until we're done ± with .NET 11 and then revert this in a month or two. I wanted to put it in main because we have all the CI tracking systems setup here and in case someone is backporting to .NET 11, they will likely merge to main first anyways.
|
jkotas
commented
Aug 31, 2026
If we want to make sure that Mono on mobile keeps working in .NET 11, we should make sure that there is right coverage in .NET 11. I assume we want to make sure that Mono on mobile keep working in .NET 11 for more than a month or two.
RC1 is "done". We have release/11.0 branch that all servicing fixes are going into. |
Summary
runtime-extra-platformsNote
This pull request description was generated by GitHub Copilot.