Skip to content

Conversation

@jmagman
Copy link
Member

@jmagman jmagman commented Jan 29, 2021

  1. Add tool_general_tests, tool_command_tests, and tool_integration_tests top-level shards.
  2. Support new subshard naming convention in web_long_running_tests and build_tests. Instead of 0, 1, 2_last with the total count (3) stored in a framework repo constant, which requires an infra commit and framework repo commit to change, instead support 1_3, 2_3, 3_3 subshard 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).
  3. Adopt subshard with new names in tool_integration_tests.
  4. Keep fallback to old naming convention so we don't have an outage between this commit and when future recipe config change propagates. This PR will test that I haven't regressed this logic on the existing try job config. Once the new config is working, I will remove the old naming parsing logic.
  5. Add smoke_test shard 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

@flutter-dashboard flutter-dashboard bot added the c: contributor-productivity Team-specific productivity, code health, technical debt. label Jan 29, 2021
@google-cla google-cla bot added the cla: yes label Jan 29, 2021
@jmagman jmagman marked this pull request as draft January 29, 2021 23:44
@jmagman jmagman force-pushed the shard-integration branch 5 times, most recently from b4a8fd9 to 7846096 Compare January 30, 2021 00:22
@jmagman jmagman marked this pull request as ready for review January 30, 2021 00:30
Copy link
Contributor

@christopherfujino christopherfujino left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks for making this change!

@fluttergithubbot fluttergithubbot merged commit 8712f63 into flutter:master Feb 1, 2021
@jmagman jmagman deleted the shard-integration branch February 1, 2021 20:59
christopherfujino pushed a commit to chris-forks/flutter that referenced this pull request Feb 3, 2021
christopherfujino added a commit that referenced this pull request Feb 3, 2021
…#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]>
@jmagman jmagman added the a: tests "flutter test", flutter_test, or one of our tests label Aug 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

a: tests "flutter test", flutter_test, or one of our tests c: contributor-productivity Team-specific productivity, code health, technical debt.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants