Balance tool_integration_tests subshards by expected duration (#195628)

Tool `integration.shard` is currently split across subshards by file
count. Each file test duration ranges from under a second to 10.5
minutes (the longest is `swift_package_manager_test`). Over the last 3
postsubmit runs Mac subshards took 4.9 to 19.9 minutes and the Windows
subshard 2.0 to 24.9. A 2 minute test is a waste of a bot, since the
setup and teardown takes much longer than that.

Split by duration instead. With the current shard counts every Mac
subshard comes out near 12 minutes, Linux near 13, Windows near 15.

Fixes #185013 (second option).
I'd like to move more of the stand-alone tool tests from the devicelab
into this shard (example https://github.com/flutter/flutter/pull/195609)
to preserve Macs in the CI pool so this balancing will let us add more
without thinking too hard about it.

### Where do these numbers come from?

The shard already runs `dart test` with `--file-reporter=json`
(`collectMetrics: true`) and `runDartTest` uploads every test result,
with its duration, to LUCI ResultDB (this was news to me).

The new `update_tool_integration_test_durations` reads those back. It
asks Buildbucket for the `tool_integration_tests` builders and their
recent successful builds, then sums per-test durations by test file. No
auth is needed to run this script. It only writes files present in the
tree. Files CI hasn't run yet keep a hand-entered value or get the host
median.

A new test in dev/bots/test (runs in `framework_tests_misc` on all
hosts) fails when the json and the files in `integration.shard`
disagree. Adding a test file without a json entry gives:
```
macos lists exactly the files in integration.shard [E]
  Not in "macos" of dev/bots/tool_integration_test_durations.json:
    test/integration.shard/my_new_feature_test.dart
  Either run:
    dart dev/bots/update_tool_integration_test_durations.dart
  or edit dev/bots/tool_integration_test_durations.json by hand. Each host needs an entry; use the
  test's wall time in seconds, or 0 on hosts where it does not run.
```
Deleted or renamed files get the matching "in the JSON but not in the
tree" message.

A wrong number only affects balance. A missing or unparseable json fails
the shard and points at the script.

## Pre-launch Checklist

- [x] I read the [Contributor Guide] and followed the process outlined
there for submitting PRs.
- [x] I read the [AI contribution guidelines] and understand my
responsibilities, or I am not using AI tools.
- [x] I read the [Tree Hygiene] wiki page, which explains my
responsibilities.
- [x] I read and followed the [Flutter Style Guide], including [Features
we expect every widget to implement].
- [x] I signed the [CLA].
- [x] I listed at least one issue that this PR fixes in the description
above.
- [x] I updated/added relevant in-code documentation (doc comments with
`///`).
- [x] If this PR introduces a new feature or capability, I created and
linked a website documentation issue or PR in [flutter/website] (or
verified none is needed).
- [x] I added new tests to check the change I am making, or this PR is
[test-exempt].
- [x] I followed the [breaking change policy] and added [Data Driven
Fixes] where supported.
- [x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel
on [Discord].

If this change needs to override an active code freeze, provide a
comment explaining why. The code freeze workflow can be overridden by
code reviewers. See pinned issues for any active code freezes with
guidance.

**Note**: The Flutter team is currently trialing the use of [Gemini Code
Assist for
GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code).
Comments from the `gemini-code-assist` bot should not be taken as
authoritative feedback from the Flutter team. If you find its comments
useful you can update your code accordingly, but if you are unsure or
disagree with the feedback, please feel free to wait for a Flutter team
member's review for guidance on which automated comments should be
addressed.

<!-- Links -->
[Contributor Guide]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview
[AI contribution guidelines]:
https://github.com/flutter/flutter/blob/main/CONTRIBUTING.ai.md
[Tree Hygiene]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md
[test-exempt]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests
[Flutter Style Guide]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md
[Features we expect every widget to implement]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement
[CLA]: https://cla.developers.google.com/
[flutter/tests]: https://github.com/flutter/tests
[flutter/website]: https://github.com/flutter/website
[breaking change policy]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes
[Discord]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md
[Data Driven Fixes]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md
6 files changed
tree: 17ef90b4c186f4ec61ce3a55ca0258e5179d9f20
  1. .agents/
  2. .claude/
  3. .gemini/
  4. .github/
  5. .vscode/
  6. agent-artifacts/
  7. bin/
  8. buildtools/
  9. dev/
  10. docs/
  11. engine/
  12. examples/
  13. packages/
  14. third_party/
  15. .autoroller-preupload.sh
  16. .ci.yaml
  17. .direnv
  18. .gitattributes
  19. .gitignore
  20. analysis_options.yaml
  21. analysis_options_common.yaml
  22. AUTHORS
  23. CHANGELOG.md
  24. CODE_OF_CONDUCT.md
  25. CODEOWNERS
  26. CONTRIBUTING.ai.md
  27. CONTRIBUTING.md
  28. dartdoc_options.yaml
  29. DEPS
  30. flutter_console.bat
  31. LICENSE
  32. PATENT_GRANT
  33. pubspec.lock
  34. pubspec.yaml
  35. README.md
  36. TESTOWNERS
README.md

Flutter CI Status Discord badge Twitter handle BlueSky badge LFX Health Score CII Best Practices SLSA 1

Flutter is Google's SDK for crafting beautiful, fast user experiences for mobile, web, and desktop from a single codebase. Flutter works with existing code, is used by developers and organizations around the world, and is free and open source.

Documentation

For release and other announcements, join the flutter-announce mailing list. Our documentation also tracks breaking changes across releases.

Terms of service

The Flutter tool may occasionally download resources from Google servers. By downloading or using the Flutter SDK, you agree to the Google Terms of Service: https://policies.google.com/terms

For example, when installed from GitHub (as opposed to from a prepackaged archive), the Flutter tool will download the Dart SDK from Google servers immediately when first run, as it is used to execute the flutter tool itself. This will also occur when Flutter is upgraded (e.g. by running the flutter upgrade command).

About Flutter

We think Flutter will help you create beautiful, fast apps, with a productive, extensible and open development model, whether you're targeting iOS or Android, web, Windows, macOS, Linux or embedding it as the UI toolkit for a platform of your choice.

Beautiful user experiences

We want to enable designers to deliver their full creative vision without being forced to water it down due to limitations of the underlying framework. Flutter‘s layered architecture gives you control over every pixel on the screen and its powerful compositing capabilities let you overlay and animate graphics, video, text, and controls without limitation. Flutter includes a full set of widgets that deliver pixel-perfect experiences whether you’re building for iOS (Cupertino) or other platforms (Material), along with support for customizing or creating entirely new visual components.

Fast results

Flutter is fast. It's powered by hardware-accelerated 2D graphics libraries like Skia (which underpins Chrome and Android) and Impeller. We architected Flutter to support glitch-free, jank-free graphics at the native speed of your device.

Flutter code is powered by the world-class Dart programming language, which enables compilation to 32-bit and 64-bit ARM machine code for iOS and Android, JavaScript and WebAssembly for the web, as well as Intel x64 and ARM for desktop devices.

Productive development

Flutter offers stateful hot reload, allowing you to make changes to your code and see the results instantly without restarting your app or losing its state.

Hot reload animation

Extensible and open model

Flutter works with any development tool (or none at all), and also includes editor plug-ins for both Visual Studio Code and IntelliJ / Android Studio. Flutter provides tens of thousands of packages to speed your development, regardless of your target platform. And accessing other native code is easy, with support for both FFI (on Android, on iOS, on macOS, on Linux, and on Windows) as well as platform-specific APIs.

Flutter is a fully open-source project, and we welcome contributions. Information on how to get started can be found in our contributor guide.