Skip to content

[devicelab] turn down android X migration gradle tests #68110

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 3 commits into from
Oct 14, 2020

Conversation

jonahwilliams
Copy link
Contributor

@jonahwilliams jonahwilliams commented Oct 14, 2020

Description

These androidx migration tests require downloading firebase, which is a large library with a number of dependencies - this causes frequent enough flakes.

AndroidX migration is ~2 years in the past, and while it would be nice to confirm this still works, ideally that would be done in a reduced manner.

@flutter-dashboard flutter-dashboard bot added the c: contributor-productivity Team-specific productivity, code health, technical debt. label Oct 14, 2020
@google-cla google-cla bot added the cla: yes label Oct 14, 2020
@jonahwilliams
Copy link
Contributor Author

It this the correct way to do it? or do I need to make recipe changes too?

@keyonghan
Copy link
Contributor

It this the correct way to do it? or do I need to make recipe changes too?

For try jobs, these changes are enough. But for prod builders, these change will only avoid status showing up on flutter-dashboard, but these builders will still run and show up in the milo dashboard. So for the prod builders, flutter/infra config changes are needed to stop running them.

@godofredoc made quite some effort to make all these hostonly devicelab tests running, will leave approval to him.

Copy link
Contributor

@godofredoc godofredoc left a comment

Choose a reason for hiding this comment

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

LGTM

@jonahwilliams jonahwilliams merged commit c11a64e into flutter:master Oct 14, 2020
@jonahwilliams jonahwilliams deleted the fix_hot_reload_crash branch October 14, 2020 20:24
@jonahwilliams
Copy link
Contributor Author

FYI @blasten , these tests have been failing on and off for the past few weeks because the LUCI bots are having problems downloading the firebase dependencies. If we can find a way to run this test with a reduced or local only dependency then it could be re-added

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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants