Repository navigation
Break up "Mac mac_unopt" #186462
Description
Mac mac_unopt has been flakey and it's a very long-running build (takes ~45 minutes), so the impact is large. See #185908.
We should consider breaking it up. A clear way to do so would be to separate host/mac builds from ios builds.
The iOS team already is planning to re-design and most likely move iOS scenario tests: #160800
Reacted by Chris Bracken
Activity
gaaclarke commentedon May 16, 2026
fyi @jtmcdole who was looking at this as well
cbracken commentedon May 19, 2026
xref to @jtmcdole's issue: #185908
flutter-triage-bot commentedon Sep 22, 2026
This issue is marked P1 but has had no recent status updates.
The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.
Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!
jmagman commentedon Nov 3, 2026
See also #155041
Run the mac_unopt sub-builds as standalone builders (flutter#195868)
Remove Mac mac_unopt builder (flutter#196027)
[CP-beta]Run the mac_unopt sub-builds as standalone builders (#196058)