[ci] Add a third web Dart unit test shard (1/2)#12138
Conversation
The web Dart unit tests are currently some of our slowest tests, and shard 2 is on the brink of hitting the 60 minute timeout. This is the first half of the process of switching from 2 shards to three shards, adding the new tasks in bringup mode but not yet changing the existing shards. Once this lands and propagates, a second PR will switch to actually using three shards. This brings us closer to our limit of 100 post-submit tasks for our wait-for-release action, but doesn't yet cross it (and we expect that limit to stop being an issue soon).
There was a problem hiding this comment.
Code Review
This pull request updates the CI configuration in .ci.yaml by adding a third shard (web_dart_unit_test_shard_3) for both the master and stable channels of the Linux web unit tests. It also adds a TODO comment regarding future adjustments to WebAssembly testing once WASM builds become the default on the stable channel. There are no review comments, and I have no feedback to provide.
|
Interestingly the wasm variant of the web unit tests is twice as fast as the non-wasm version (the actual testing looks like it's more than twice as fast, but there's fixed overhead for things like setting up the bot and fetching all the deps for the packages). |
| @@ -216,7 +217,20 @@ targets: | |||
| version_file: flutter_stable.version | |||
| package_sharding: "--shardIndex 1 --shardCount 2" | |||
There was a problem hiding this comment.
what is shardCount? should it not go to 3 on the other shards? or are index and count just the same thing but off by 1?
|
Since the tree status is currently red because |
|
Detected the If you add the The "Merge" button is also unlocked. To bypass presubmits as well as the tree status, press the GitHub "Add to Merge Queue". |
…r#189194) flutter/packages@52d84d6...20928d5 2026-07-09 44525804+sailendrabathi@users.noreply.github.com [video_player_android] Implement backBufferDurationMs in ExoPlayer (flutter/packages#12124) 2026-07-09 bolling.ludwig@gmail.com [camera_platform_interface] Make setJpegImageQuality default a no-op (flutter/packages#12123) 2026-07-09 36081049+anirudhsharma392@users.noreply.github.com [local_auth] Clarify getAvailableBiometrics documentation regarding iOS permissions (flutter/packages#11901) 2026-07-09 stuartmorgan@google.com [ci] Add a third web Dart unit test shard (2/2) (flutter/packages#12150) 2026-07-08 stuartmorgan@google.com [ci] Add a third web Dart unit test shard (1/2) (flutter/packages#12138) 2026-07-08 43054281+camsim99@users.noreply.github.com Add pre-commit hook to verify static analysis passes & format is correct (flutter/packages#11941) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-packages-flutter-autoroll Please CC flutter-ecosystem@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
The web Dart unit tests are currently some of our slowest tests, and shard 2 is on the brink of hitting the 60 minute timeout. This is the first half of the process of switching from 2 shards to three shards, adding the new tasks in bringup mode but not yet changing the existing shards. Once this lands and propagates, a second PR will switch to actually using three shards.
This brings us closer to our limit of 100 post-submit tasks for our wait-for-release action, but doesn't yet cross it (and we expect that limit to stop being an issue soon).