Split tools_tests subshards into separate shards to support sub-sub-sharding#75033
Conversation
b4158e6 to
afa707f
Compare
b4a8fd9 to
7846096
Compare
7846096 to
a336773
Compare
a336773 to
5af1d57
Compare
|
Windows tool_tests are still running, but this seems to not have regressed the current config behavior: All smoke tests are running, and the right shard is being selected. |
christopherfujino
left a comment
There was a problem hiding this comment.
LGTM. Thanks for making this change!
…#75303) * Only show devtools deep links for render overflow errors (#74916) * Add fixes for nullOk changes (#74866) * [flutter_tools] delete old directories when unzipping ontop of them (#74818) Fixes #74772 stale files from previous SDKs were getting left in the cache, confusing the analyzer. * Make flutter create --smaple null-safe (#74844) * Suppress 'Info: Compiling without sound null safety' message when building flutter_tools (#74740) The CFE now logs to stdout by default when compiling a program which has non-null-safe dependencies. Since flutter_tools has not yet migrated, we need to suppress this message when compiling the tool. Fixes #74366 * Split tools_tests subshards into separate shards to support sub-sub-sharding (#75033) * Adopt tool_test shard builders (#75171) * Adopt subshard naming convention in build_tests (#75179) * Mark tool_integration_tests not flaky (#75273) * roll flutter/plugins to ToT to fix analysis error * update engine hash Co-authored-by: Kenzie Schmoll <[email protected]> Co-authored-by: Kate Lovett <[email protected]> Co-authored-by: Jonah Williams <[email protected]> Co-authored-by: Michael Goderbauer <[email protected]> Co-authored-by: Ben Konyi <[email protected]> Co-authored-by: Jenn Magder <[email protected]>
tool_general_tests,tool_command_tests, andtool_integration_teststop-level shards.web_long_running_testsandbuild_tests. Instead of0,1,2_lastwith the total count (3) stored in a framework repo constant, which requires an infra commit and framework repo commit to change, instead support1_3,2_3,3_3subshard names where the total number is encoded in the name. This allows shard numbers to be changed in the config without a corresponding framework commit.Use one-indexing for sanity so it's not (0 of 2, 1 of 2).
tool_integration_tests.smoke_testshard and support subsharding there. Add integration tests using this shard to test the subsharding logic.Infra side at https://github.com/flutter/infra/pull/339
Framework part of #75003