8000 Adopt tool_test shard builders by jmagman · Pull Request #75171 · flutter/flutter · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Adopt tool_test shard builders #75171

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 2, 2021

Conversation

jmagman
Copy link
Member
@jmagman jmagman commented Feb 1, 2021

Adopt tool_integration_tests builder from https://github.com/flutter/infra/pull/339 to test #75033.

Example tool_integration_tests run:
Screen Shot 2021-02-01 at 3 47 46 PM

Remove tool_general_tests and tool_command_tests introduced in #75033 since shards without subshards is evidently not supported (see https://github.com/flutter/infra/pull/340). Support these subshards in tool_tests and simplify the subshard selecting logic in the runner.

Fixes #75003

8000
@jmagman jmagman added the c: contributor-productivity Team-specific productivity, code health, technical debt. label Feb 1, 2021
@jmagman jmagman self-assigned this Feb 1, 2021
@google-cla google-cla bot added the cla: yes label Feb 1, 2021
@jmagman jmagman force-pushed the shard-builder-json branch from d263474 to d16495a Compare February 1, 2021 21:44
@flutter-dashboard
Copy link

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat.

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

@jmagman jmagman force-pushed the shard-builder-json branch from 1ceffe6 to 14cff69 Compare February 1, 2021 23:14
@@ -384,7 +398,15 @@
"name": "Windows tool_tests",
"repo": "flutter",
"task_name": "win_tool_tests",
"enabled":true
"enabled":true,
"run_if":["dev/**", "packages/flutter_tools/**", "bin/**"]
Copy link
Member Author

Choose a reason for hiding this comment

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

run_if was missing?

@jmagman
Copy link
Member Author
jmagman commented Feb 2, 2021

@jmagman jmagman requested a review from jonahwilliams February 2, 2021 02:58
Copy link
Member
@jonahwilliams jonahwilliams left a comment

Choose a reason for hiding this comment

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

LGTM ship it!

@fluttergithubbot fluttergithubbot merged commit f761ae2 into flutter:master Feb 2, 2021
@jmagman jmagman deleted the shard-builder-json branch February 2, 2021 19:02
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 <43759233+kenzieschmoll@users.noreply.github.com>
Co-authored-by: Kate Lovett <katelovett@google.com>
Co-authored-by: Jonah Williams <jonahwilliams@google.com>
Co-authored-by: Michael Goderbauer <goderbauer@google.com>
Co-authored-by: Ben Konyi <bkonyi@google.com>
Co-authored-by: Jenn Magder <magder@google.com>
@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.

tool_tests integration shard should be split up
3 participants
0