-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Upgrade integration tests to use AGP 7.3/Gradle 7.4 #129642
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
Conversation
|
This may also unblock #122779 (see this comment), though the changes are worth landing independently. |
camsim99
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Can you note in the description where AGP was downgraded? I assume it's not a problem but may be good to remember.
Updated the description to link to the two places |
|
As a follow up it might be good to make the shards these tests use for a specific platform (e.g. Mac build_tests_1_4,...,Mac build_tests_4_4) share a common configuration, or at least have a comment noting changes should be made to all shards. Otherwise the test behavior is implicitly relying on the current distribution of tests across the shards, which makes it easy to introduce issues like this where failures only manifest on later, unrelated PRs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible and should we try and use named constants for these version numbers (here and elsewhere)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could definitely make the templates use the values of some constants when generating the new build.gradle that we use to overwrite the existing (and link it to the versions we use to generate the build.gradle in new projects, if we wanted).
I'm actually not sure how lockfile generation would work if we made the values in the generated build.gradles be constants, though. My guess is that it would generate lockfiles based on the value of the constant, which would mean that whenever we updated the constant we would still need to re-run lockfile generation, essentially "replacing" the value anyways (with itself again). I can try it out though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From testing it looks like constants in the build.gradle get resolved to their values in the lockfiles, so if we did use a constant in the generated build.gradle, it would still resolve to a specific value in the lockfile that wouldn't change in line with updates to the constant. So we would still need to re-run the script, which replaces the value in the generated build.gradle anyways.
I do think it could make sense to have the values in the generate_gradle_lockfiles.dart templates be constants, especially if we did want them to be the same as the values in templates we use to make a new project. I'll file an issue where we can make the decision (#129747).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SGTM.
|
It looks like previous versions of similar PRs have had a tendency to break in postsubmit (see d155bc1, 1e69683, 7165339). cc'ing @christopherfujino as I see you've reviewed some of these past PRs - I tried running the devicelab tests that looked relevant to the tests I changed as outlined here, and I didn't run into any issues. Is there anything else you would recommend trying before merging? There still isn't a good way to run postsubmits before submitting, is there? |
You can test devicelab targets by temporarily changing |
Awesome, thanks I'll try that! |
|
There were some failures in enabling the post-submits, but I checked the logs for each one and they all seemed infra-related (they never started for some reason). Most passed though, and nothing indicated a problem with this change, so I'm going to go ahead and add autosubmit. |
|
auto label is removed for flutter/flutter, pr: 129642, due to - The status or check suite Mac customer_testing has failed. Please fix the issues identified (or deflake) before re-applying this label. |
I'm working on fixing this upstream. You will have to rebase (not merge) upstream once the tree is fixed to fix the tests on your branch. |
…st for testing" This reverts commit 72bdd7a8917783c1d5a6c42950cd2c85f63d6988.
aecb663 to
e78f6fb
Compare
|
It looks like this caused two runs of the Either way it shouldn't cause problems for future commits, though it may affect some presubmits until people merge or rebase. |
It's actually that these configurations are generated by a post-submit job, so there's always some lag between when the PR lands and when they take effect: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20ci_yaml%20flutter%20roller/9809/overview |
|
Oh, and it looks like these ran out of order https://ci.chromium.org/ui/p/flutter/builders/luci.flutter.prod/Linux%20ci_yaml%20flutter%20roller This is already being tracked in #127063 |
flutter/flutter@ff838bc...aa5f4a2 2023-07-01 [email protected] Enable no_wildcard_variable_uses lint (flutter/flutter#129858) 2023-06-30 [email protected] mark packages-autoroller bringup again (flutter/flutter#129859) 2023-06-30 [email protected] Update `SwitchTheme` tests for M2/M3 (flutter/flutter#129811) 2023-06-30 [email protected] Change pub roller bot to push to flutter-pub-roller-bot/flutter.git (flutter/flutter#129844) 2023-06-30 [email protected] Fix NetworkImage causing spurious warning in tests (flutter/flutter#129537) 2023-06-30 [email protected] Roll Flutter Engine from 54b573e9c4e5 to e6b8292705a8 (4 revisions) (flutter/flutter#129852) 2023-06-30 [email protected] Upgrade integration tests to use AGP 7.3/Gradle 7.4 (flutter/flutter#129642) 2023-06-30 [email protected] Roll Packages from d4752c4 to 53ed5a0 (5 revisions) (flutter/flutter#129837) 2023-06-30 [email protected] Updated correct tasks for test ownership fix (flutter/flutter#129812) 2023-06-30 [email protected] Updated some golden image tests for M2/M3 (flutter/flutter#129794) 2023-06-30 [email protected] Remove an unnecessary assert (flutter/flutter#129796) 2023-06-30 [email protected] Update `Radio` tests for M2/M3 (flutter/flutter#129814) 2023-06-30 [email protected] Update `Switch` tests for M2/M3 (flutter/flutter#129810) 2023-06-30 [email protected] Roll Flutter Engine from 099a70ebbc60 to 54b573e9c4e5 (1 revision) (flutter/flutter#129821) 2023-06-30 [email protected] Update `SwitchListTile` tests for M2/M3 (flutter/flutter#129809) 2023-06-30 [email protected] Fix `NavigationDrawer` selected item has wrong icon color (flutter/flutter#129625) 2023-06-30 [email protected] Update basic_test.dart for M3 compliance (flutter/flutter#129714) 2023-06-30 [email protected] Roll Flutter Engine from d33343430f18 to 099a70ebbc60 (7 revisions) (flutter/flutter#129818) 2023-06-30 [email protected] Roll Flutter Engine from 68cc1a7971d5 to d33343430f18 (2 revisions) (flutter/flutter#129801) 2023-06-30 [email protected] Revert no-response to fork. (flutter/flutter#129775) 2023-06-30 [email protected] Make `DropdownMenu` be able to scroll to the highlighted item when searching. (flutter/flutter#129740) 2023-06-29 [email protected] Roll Flutter Engine from cd9ce66db14a to 68cc1a7971d5 (10 revisions) (flutter/flutter#129799) 2023-06-29 49699333+dependabot[bot]@users.noreply.github.com Bump actions/labeler from 4.1.0 to 4.2.0 (flutter/flutter#129797) 2023-06-29 [email protected] Roll Flutter Engine from eabb22900b44 to cd9ce66db14a (1 revision) (flutter/flutter#129756) 2023-06-29 [email protected] Remove `@NonNull` to avoid warning (flutter/flutter#129472) 2023-06-29 [email protected] Remove use of any (flutter/flutter#129793) 2023-06-29 [email protected] Prepare for utf8.encode() to return more precise Uint8List type (flutter/flutter#129769) 2023-06-29 [email protected] Deletes files that should be ignored (flutter/flutter#127984) 2023-06-29 [email protected] Fix flutter_plugins by rolling revision (flutter/flutter#129781) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-packages Please CC [email protected],[email protected],[email protected] on the revert to ensure that a human is aware of the problem. To file a bug in Packages: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Upgrades tests under
dev/integration_teststo use the latest values in the templates. Most of this PR was auto-generated, by runningfind dev/integration_tests/ -type d -name 'android' | dart dev/tools/bin/generate_gradle_lockfiles.dartfrom the root of the flutter directory.The pieces that were not are:
firebaselab/firebaselabrecipe. Previously they had no java dependency, and were therefore defaulting to java 1.8. The newer AGP versions necessitated an upgrade to 11 to run.Note that it also ended up downgrading the AGP version in two places (in the hybrid_android_views and platform_interaction tests), because those had been manually edited to a newer version than the template.
Related to: #123636, #123910
Pre-launch Checklist
///).If you need help, consider asking for advice on the #hackers-new channel on Discord.