In the default CI set that runs automatically when a change is made to src/coreclr, only priority 0 test legs are executed for osx-arm64. Meanwhile, for osx-x64, the libraries debug tests are run by default alongside the priority 0 tests. Given that Apple has moved to ARM64 (Apple Silicon) as the primary architecture, it seems logical to prioritize osx-arm64 in the default CI, rather than osx-x64.
Currently, we can manually trigger the osx-arm64 libraries debug tests if needed, but they are not part of the automatic/default test set.
If expanding the CI set for osx-arm64 leads to longer test cycles, it may be worth considering the trade-off between testing time and coverage, or potentially rebalancing the priority of osx-x64 tests.
In the default CI set that runs automatically when a change is made to
src/coreclr
, only priority 0 test legs are executed forosx-arm64
. Meanwhile, forosx-x64
, the libraries debug tests are run by default alongside the priority 0 tests. Given that Apple has moved to ARM64 (Apple Silicon) as the primary architecture, it seems logical to prioritizeosx-arm64
in the default CI, rather thanosx-x64
.Currently, we can manually trigger the
osx-arm64
libraries debug tests if needed, but they are not part of the automatic/default test set.If expanding the CI set for
osx-arm64
leads to longer test cycles, it may be worth considering the trade-off between testing time and coverage, or potentially rebalancing the priority ofosx-x64
tests.