@keyonghan what else needs to be done to make sure the arm64 cipd packages are used on arm bots, and Rosetta is installed?

https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20module_test_ios/17563/overview

Target aot_assembly_release failed: ProcessException: Bad CPU type in executable

https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20build_tests_1_4/26563/overview

  failed to resolve flutter_internal/browsers/chrome/mac-arm64@version:98.1 (line 1): no such package: flutter_internal/browsers/chrome/mac-arm64

Ideally this behavior is tied to the cpu property of the bot and not the name of the task/builder so that it can run on any bot with any architecture, given available capacity.

#87508

For Rosetta, filed https://bugs.chromium.org/p/chromium/issues/detail?id=1354817
For arm64 cipd packages, we need the package maintainer to add the arm64 version, for example chrome.

For arm64 cipd packages, we need the package maintainer to add the arm64 version, for example chrome.

This one failed missing openjdk but we should have that? #98532
https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20framework_tests_misc/25668/overview

And this one is missing arm ffi
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8805363977658226209/+/u/run_test.dart_for_tool_host_cross_arch_tests_shard_and_subshard_None/test_stdout

https://chrome-infra-packages.appspot.com/p/flutter/ruby/mac-arm64/+/P1b-yT8l6N4J6TbVI5fJDqmbWIKP6WhKcLfITjWZ2ZEC
#87508 (comment)

This one failed missing openjdk but we should have that? #98532
https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20framework_tests_misc/25668/overview

#110110 to fix.

For arm64 cipd packages, we need the package maintainer to add the arm64 version, for example chrome.

Filed #110113

@keyonghan everything passed when I added the arm64 tag. If we want Mac to work for either, we can't set it in .ci.yaml, it should be derived from the cpu property. Where is that tag used?

@keyonghan everything passed when I added the arm64 tag. If we want Mac to work for either, we can't set it in .ci.yaml, it should be derived from the cpu property. Where is that tag used?

Wait, that tag didn't even get applied? I guess the tags on the individual tasks override it, not add to it?

          "tags": [
                "devicelab",
                "hostonly"
              ],

https://chromium-swarm.appspot.com/task?id=5ce567548c6b2a10&o=true&w=true

Hm the passing tests actually ran on x86 even though they had the cpu arm64 property:
https://chromium-swarm.appspot.com/task?id=5ce5675befae1110&o=true&w=true

cpu:x86x86-64x86-64-i7-8700B

        "requested_properties": {
...
            "cpu": "arm64",

@keyonghan everything passed when I added the arm64 tag. If we want Mac to work for either, we can't set it in .ci.yaml, it should be derived from the cpu property. Where is that tag used?

The tag is used only for data analysis purpose, and it should not affect platform selection.
Sounds something wrong when fetching properties/dimensions from PR to overriding the scheduled build config, though the first commit did pick up the changes in the PR.

Blocked on getting Rosetta on these machines https://bugs.chromium.org/p/chromium/issues/detail?id=1354817

Hm the passing tests actually ran on x86 even though they had the cpu arm64 property

This happened again...

Filed #110561 to install arm Ruby on arm bots.