Skip to content

Reverts "Implement dartPluginClass support for plugins #74469" - #78623

Merged
zanderso merged 6 commits into
masterfrom
revert-74469
Mar 23, 2021
Merged

zanderso merged 6 commits into
masterfrom
revert-74469

Conversation

@zanderso

Copy link
Copy Markdown
Member

For #78554

@flutter-dashboard flutter-dashboard Bot added d: examples Sample code and demos c: contributor-productivity Team-specific productivity, code health, technical debt. tool Affects the "flutter" command-line tool. See also t: labels. labels Mar 19, 2021
@google-cla google-cla Bot added the cla: yes label Mar 19, 2021
@zanderso
zanderso requested a review from jonahwilliams March 19, 2021 21:00

@jonahwilliams jonahwilliams left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

@jmagman

jmagman commented Mar 19, 2021

Copy link
Copy Markdown
Member

Some conflicts here. 😞

@zanderso
zanderso force-pushed the revert-74469 branch 3 times, most recently from 95c2115 to 1627ce5 Compare March 23, 2021 15:28
@zanderso

Copy link
Copy Markdown
Member Author

@jonahwilliams Do you know how (or whether) to remove the "Mac dart_plugin_registry_test" presubmit check for this?

@jonahwilliams

Copy link
Copy Markdown
Contributor

For the try builders, you need to edit the JSON config here to say enabled: false:

https://github.com/flutter/flutter/blob/master/dev/try_builders.json#L535

and maybe for prod builders just mark it as flaky?

https://github.com/flutter/flutter/blob/master/dev/prod_builders.json#L904

How do we disable a prod builder? @godofredoc / @keyonghan

Comment thread dev/try_builders.json
"run_if": ["dev/**", "packages/flutter_tools/**", "bin/**"]
},
{
"name": "Mac dart_plugin_registry_test",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Do you know how (or whether) to remove the "Mac dart_plugin_registry_test" presubmit check for this?

I would have thought this would have done it...

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

oh, I wonder if uses the JSON from HEAD?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@keyonghan why would it show up in this PR as a pre-submit check if it was removed from try_builders?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

It should be reflected in the PR immediately.
There is some recent change about how builders are retrieved. /cc @CaseyHillers any idea?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I just edited the try_builders.json in #78888 and the two tests I added showed up...

@keyonghan keyonghan Mar 23, 2021 •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Was the try_builders.json change here in the first commit change of this PR? I am guessing if it was triggered first, then it will remain in this check run set. Though later changes (remove that test) only trigger other tests.

@keyonghan

Copy link
Copy Markdown
Contributor

For the try builders, you need to edit the JSON config here to say enabled: false:

https://github.com/flutter/flutter/blob/master/dev/try_builders.json#L535

and maybe for prod builders just mark it as flaky?

https://github.com/flutter/flutter/blob/master/dev/prod_builders.json#L904

How do we disable a prod builder? @godofredoc / @keyonghan

Marking it as flaky will hide it from tree status, but it will still be scheduled to run.
At this moment, if we want to drop that test completely for post submit tests, we need to remove the builder config from flutter/infra.

@jonahwilliams

Copy link
Copy Markdown
Contributor

We need to remove it for 2-3 weeks or so

@keyonghan

Copy link
Copy Markdown
Contributor

We need to remove it for 2-3 weeks or so

Then marking as flaky sounds a better way to go.

Comment thread dev/try_builders.json
"name": "Mac dart_plugin_registry_test",
"repo": "flutter",
"task_name": "dart_plugin_registry_test",
"enabled": true,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Another option: you can set "enabled": false if you want to reenable it back later.

@zanderso

Copy link
Copy Markdown
Member Author

I restored the entries to the json files, and marked as flaky in prod and disabled in try.

@zanderso
zanderso merged commit 5efc716 into master Mar 23, 2021
@zanderso
zanderso deleted the revert-74469 branch March 23, 2021 21:28
@zanderso

Copy link
Copy Markdown
Member Author

/cc @blasten

blasten pushed a commit to blasten/flutter that referenced this pull request Apr 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c: contributor-productivity Team-specific productivity, code health, technical debt. d: examples Sample code and demos tool Affects the "flutter" command-line tool. See also t: labels.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants