Jenn Magder

Example failure: ``` [2024-07-11 15:55:28.438858] [STDOUT] run:stderr: 2024-07-11 15:55:28.435 xcodebuild[19672:128982] Writing error result bundle to /var/folders/cs/cqkgmb4n27n6k5bhvx0_34d00000gp/T/ResultBundle_2024-11-07_15-55-0028.xcresult [2024-07-11 15:55:28.470962] [STDOUT] run:stderr: xcodebuild: error: unreadable input ' arch=arm64' at end of value...

Heads up, after https://github.com/flutter/flutter/pull/152347 you'll be able to grab the `ARCH` build settings before the actual compilation happens.

Thank you for your contribution. I'm going to close this PR for now since there are outstanding comments, just to get this off our PR review queue. Please don't hesitate...

If it's the try pool then likely from the PRs where I was testing Xcode 16+ https://github.com/flutter/engine/pull/55053 https://github.com/flutter/packages/pull/7484 https://github.com/flutter/flutter/pull/155980 I thought the caches handled Xcode versions, and it even cleaned...

Given how many Mac subbuilds happen on a single engine PR (see https://github.com/flutter/engine/pull/55053 [related builds](https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20Engine%20Drone/1325174/related-builds)), then add in framework and packages and maybe me pushing ~2x per PR and re-running...

I wonder why clearing the cache (even if they are shared) work when corruption is detected? https://flutter-review.googlesource.com/c/recipes/+/52421

> Also, interestingly, when `xcodebuild` commands hang, opening the Xcode app (via `open` command) also hangs. This makes me think maybe it's a dialog that's blocking. What's are the launch...

You're going to want the spindump for the machine, not just the hung process, which is waiting for a response from an XPC service poking to another process, in this...

Does the all packages test project also need to be updated? https://github.com/flutter/packages/blob/3515abab07d0bb2441277f43c2411c9b5e4ecf94/.ci/legacy_project/all_packages/android/app/build.gradle#L25 https://github.com/flutter/packages/blob/3515abab07d0bb2441277f43c2411c9b5e4ecf94/.ci/legacy_project/all_packages/android/settings.gradle#L11 I noticed it here https://github.com/flutter/packages/pull/8328 https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8728179667738494273/+/u/Run_package_tests/build_all_packages_for_Android_-_legacy_version/stdout https://github.com/flutter/packages/tree/3515abab07d0bb2441277f43c2411c9b5e4ecf94/.ci/legacy_project#readme > Updates over time should be minimal. We don't expect...

I know this issue is ancient but the out-of-date numbers came up again, this page is even further out of date, particularly post-Impeller launch. cc @jonahwilliams in case this is...