Jenn Magder

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", ```

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 https://github.com/flutter/flutter/issues/110561 to install arm Ruby on arm bots.

> Shall we note somewhere (maybe in the wiki) that for any new Mac host only target, the owner should validate it works on both arches? Which wiki were you...

I'm going to block this until https://github.com/flutter/flutter/issues/110561 is done, it's causing too many failures on arm, and it's too possible for devs adding new tests to have it pass in...

Trying all arm tests again on top of https://github.com/flutter/flutter/issues/110561.

This is ready for review now. The x64 tests remaining are related to the missing arm Chrome cipd package, and the web team is looking into that: https://github.com/flutter/flutter/issues/110113

Though when I fix the TypeError it crashes later: ``` Bad state: Cannot add event after closing ``` the event is `{\"jsonrpc\":\"2.0\",\"method\":\"streamCpuSamplesWithUserTag\",\"id\":26,\"params\":{\"userTags\":[]}}`, something is still adding to a stream.

No idea why this is happening only on an M1 simulator.