Migrate macos jobs to macos_arm64#173
Conversation
|
NOTE: An alternative is to change the BazelCI platform from |
|
Why are we polluting rules repo configs if the issue is in how Bazel CI is configured/deployed? Surely we should instead just not set these vars in |
|
I would argue that it's also not good to specialize BazelCI to do special behavior for just one platform-type due to technical limitations of the underlying system. WDYT about this instead:
AFAIK there's no real need for rules_testing to test on Intel Macs specifically, and the arm64 Macs in BazelCI are faster. |
152816e to
621fc20
Compare
|
Changed the scope of this PR to migrate |
hvadehra
left a comment
There was a problem hiding this comment.
Thanks. Do you know when you expect things to start failing without this change?
|
In 1-2 weeks, after I land bazelbuild/bazel#29854 |
The Intel
macosdeployment in BazelCI does not have the latest Android build tools installed. By default, BazelCI addsANDROID*environment variables to builds, which registers an Android toolchain for any transitively-loaded Android deps, which causes a repo rule-level error.To prevent this, this PR migrates
macosjobs tomacos_arm64.