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
{{ message }}
Repository navigation
[chore] Split up long-running tool_integration_tests to have more balanced sharding #185013
I think just creating more shards or giving a longer timeout to the shards is the wrong solution here. Instead we should try to get the tests more balanced across the shards.
Some ideas for solving this issue:
Change tests that run multiple tests in one file to separate test files, so they get distributed more.
Create a list of long-running tests in _runIntegrationToolTests and forcibly assign them to different shards.
Yeah, I think 1. is the best solution. Realistically, we shouldn't be placing multiple integration tests in the same file, but we haven't really been consistent with that
11 to 41 minutes. Splitting up the tests I own at least prevents timeouts now.
@bkonyi I think this is for you to decide whether you want to prio tracking down other tests that could use splitting up from the 41 and 37 minute bots.
Yeah, I think this is enough evidence to show that smaller test libraries results in increased granularity when it comes to sharding, which should better distribute slower tests across all the shards. We should really get into the habit as a team to create multiple test files for features rather than shoving multiple related tests into the same library.
This is something I can take on. I'll start with the integration tests, but will also investigate how we can restructure the tool's test suite overall.
This issue is assigned to @bkonyi but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!
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 -v and a minimal reproduction of the issue.
Activity
saurabh-mirajkar commentedon Apr 14, 2026
@dcharkes Thanks for the report. Labelling for
team-infrato investigate further.[ci] Split up integration.shard record_use_test.dart (#185022)
[ci] Split up integration.shard native_assets_test.dart (#185020)
[ci] Split up integration.shard dart_data_asset_test.dart (#185021)
[ci] Split up integration.shard record_use_test.dart (flutter#185022)
[ci] Split up integration.shard native_assets_test.dart (flutter#185020)
[ci] Split up integration.shard dart_data_asset_test.dart (flutter#18…
jtmcdole commentedon Apr 20, 2026
team-infra is not the right team.
dcharkes commentedon Apr 21, 2026
11 to 41 minutes. Splitting up the tests I own at least prevents timeouts now.
@bkonyi I think this is for you to decide whether you want to prio tracking down other tests that could use splitting up from the 41 and 37 minute bots.
bkonyi commentedon Apr 21, 2026
Yeah, I think this is enough evidence to show that smaller test libraries results in increased granularity when it comes to sharding, which should better distribute slower tests across all the shards. We should really get into the habit as a team to create multiple test files for features rather than shoving multiple related tests into the same library.
This is something I can take on. I'll start with the integration tests, but will also investigate how we can restructure the tool's test suite overall.
flutter-triage-bot commentedon Aug 25, 2026
This issue is assigned to @bkonyi but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!
jmagman commentedon Oct 29, 2026
Hey @bkonyi this is assigned to you but I had an idea for how to do this: #195628
Balance tool_integration_tests subshards by expected duration (flutte…
Balance tool_integration_tests subshards by expected duration (flutte…
github-actions commentedon Nov 16, 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.