Repository navigation
Closed
Copy link
Labels
a: tests"flutter test", flutter_test, or one of our tests"flutter test", flutter_test, or one of our testsc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.team-toolOwned by Flutter Tool teamOwned by Flutter Tool teamtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.
Description
| Builder | Machine Type | P25 Duration In Minutes | Average Duration In Minutes | P75 Duration In Minutes | Total Builds | Duration Bucket |
|---|---|---|---|---|---|---|
| Mac tool_integration_tests_4_5 | n1-highcpu-8 | 33.62 | 34.72 | 34.97 | 88 | 30-35 |
| Mac tool_integration_tests_1_5 | n1-highcpu-8 | 30.68 | 31.45 | 31.73 | 90 | 30-35 |
| Mac tool_integration_tests_5_5 | n1-highcpu-8 | 29.48 | 30.40 | 30.87 | 89 | 30-35 |
| Mac tool_integration_tests_3_5 | n1-highcpu-8 | 20.30 | 20.68 | 21.53 | 95 | 20-25 |
| Mac tool_integration_tests_2_5 | n1-highcpu-8 | 16.03 | 16.76 | 16.90 | 83 | 15-20 |
All 5 Mac tool_integration_tests_* are regularly taking more than the targeted 10-15 minutes. While we could be smarter about bucketing, we could also take the easier road and just increase the number of subshards. Mac currently has 5 shards. For comparison, Windows has 10 and Linux has 7. Increase the number of shards until each are under 15 minutes.
If there are still outliers then consider smarter organization, like pulling out the longest running ones into separate shards.
Currently, the try pool capacity for this test is 129 bots and the prod pool has 56 bots.
Set like this:
Line 4576 in bcabd8e
| - name: Mac tool_integration_tests_1_5 |
Line 4591 in bcabd8e
| subshard: "1_5" |
Metadata
Metadata
Assignees
Labels
a: tests"flutter test", flutter_test, or one of our tests"flutter test", flutter_test, or one of our testsc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.team-toolOwned by Flutter Tool teamOwned by Flutter Tool teamtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.
Activity
jmagman commentedon Jul 7, 2026
@jtmcdole it would be helpful if "Flutter Builders Machine Times" included queue time metrics. If I go extreme and make 100 shards, then individual build time will be very small, but we would saturate capacity and queue time would increase.
go/flutter-infra-metrics has queue time under Devicelab LUCI metrics, for example.
[-]"Mac tool_integration_tests" builds take too long, add shards[/-][+]"Mac tool_integration_tests" builds take too long, add subshards[/+]jtmcdole commentedon Jul 9, 2026
Good ask - I bet we have that tracked in BigQuery somewhere.
jtmcdole commentedon Jul 9, 2026
Done.
8 remaining items
jmagman commentedon Jul 10, 2026
#189040 landed, but the new builder
Mac tool_integration_tests_1didn't show up, and the old ones likeMac tool_integration_tests_1_5disappeared and reappeared:Infra team, did something go wrong with the infra config syncing?
jmagman commentedon Jul 13, 2026
It showed up, guess it took another commit to sync.
Take Mac tool_integration_tests_* out of bringup (flutter#189368)
[CP-beta]Increase number of 'Mac tool_integration_tests' subshards (#…
[CP-stable]Increase number of 'Mac tool_integration_tests' subshards (#…
[CP-beta]Increase number of 'Mac tool_integration_tests' subshards fr…
github-actions commentedon Jul 27, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.