Zachary Anderson

> Could potentially run `./gradlew dependencies` as an infra step before to download dependencies https://stackoverflow.com/questions/50183848/gradle-task-to-only-download-maven-dependencies/50219857#50219857 That sounds promising. It would also allow scoping retries down to the infra step by...

It sounds like the question is how to add an infra step like in https://flutter-review.googlesource.com/c/recipes/+/45320 to the engine v2 android build configs like in https://github.com/flutter/engine/blob/main/ci/builders/linux_android_debug_engine.json. I think @godofredoc would know...

@godofredoc is OOO, but maybe @keyonghan knows if it's possible to add something like https://flutter-review.googlesource.com/c/recipes/+/45320 as an optional step to an engine v2 config?

Seeing on some other tests as well https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8747865981990983953/+/u/test:_Host_Tests_for_host_debug_unopt/stdout. Are these unit tests running in parallel? Wondering if there are races.

I found out how to remove a bot from the pool. 1. `git clone https://chrome-internal.googlesource.com/infradata/config` 2. Edit https://chrome-internal.googlesource.com/infradata/config/+/refs/heads/main/configs/chromium-swarm/starlark/bots/flutter.star 3. Run `./main.star` at the root of that repo. 4. Upload the...

The bot was re-imaged as a first step before removing it from service. We'll have to continue monitoring for continued failures on the same bot.

This PR does that, but I had to disable the macOS desktop unit tests since they were flaky on arm64: https://github.com/flutter/engine/pull/55882. This PR should be heavily scrutinized.

We've experimented with a `--quiet` flag to `run_tests.py` which causes it to only output anything when a test fails. @jason-simmons reverted one instance of that experiment, but I'm forgetting why...

Yes, I'll edit the README. Working on the text, but I think this PR doesn't need to block on it? A while back, @domesticmouse volunteered to be the owner for...

> I wonder if we should default to building Dart SDK from source from third_party/dart when using `et` I'd recommend against this because it will slow down local engine development...