You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
Activity
jtmcdole commentedon May 1, 2026
This task takes 46+ minutes and has an outsized impact on tree closure. Marked as supressed.
Recent failures:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac%20Production%20Engine%20Drone/964188/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac%20Production%20Engine%20Drone/964342/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac%20Production%20Engine%20Drone/964783/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac%20Production%20Engine%20Drone/963311/overview
jmagman commentedon May 1, 2026
Infra error mounting the iOS simulator runtime:
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8683177437043962081/+/u/install_runtimes__2_/verify_and_mount_runtime_ios-26-2_17c52/stdout
jmagman commentedon May 1, 2026
Likely many are timeouts from the Xcode 26 install cache propagating.
jmagman commentedon May 1, 2026
Confusingly, the actually failing test here https://ci.chromium.org/ui/p/flutter/builders/prod/Mac%20Production%20Engine%20Drone/967460/infra
is showing up as an infra failure because it's trying to run again (to deflake?) and the second run hits the 1hr timeout.
Failure is:
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8682975853707086849/+/u/test:_Host_Tests_for_host_debug_unopt_arm64/stdout
jmagman commentedon May 1, 2026
This one is mounting a git cache for 32 minutes?
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac%20Production%20Engine%20Drone/963311/overview
#185767
saurabh-mirajkar commentedon May 4, 2026
Thanks for the detailed report. Labeling and routing to
team-infrafor further investigation.flutter-triage-bot commentedon May 4, 2026
The
fyi-infralabel is redundant with theteam-infralabel.7 remaining items
jtmcdole commentedon Jul 6, 2026
Still flakey: https://ci.chromium.org/ui/p/flutter/builders/luci.flutter.prod/Mac%20mac_unopt
testStaticLogInfoDoesNotEvaluateMessageBelowLogLevelflakey #194776FlutterWindowControllerSizeTest.SizedToContentNotResizableflakey #194780testSceneWillConnectToSessionOptionsHandledByApplicationPluginMultipleEnginesflakey #194779Run the mac_unopt sub-builds as standalone builders (flutter#195868)
Split mac_host_{debug,profile,release}_arm64_tests into one step per …
flutter-triage-bot commentedon Nov 10, 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!