-
Notifications
You must be signed in to change notification settings - Fork 28.7k
add run_gradle_lock_files_check.dart for new PR's that modify gradle files #169245
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
base: master
Are you sure you want to change the base?
add run_gradle_lock_files_check.dart for new PR's that modify gradle files #169245
Conversation
c6cf8ad
to
d1344bd
Compare
…ges' into feat/gradle_lock_files#test_changes
…ges' into feat/gradle_lock_files#test_changes
converting to a draft because I think it is still in progress. |
This pull request has been changed to a draft. The currently pending flutter-gold status will not be able to resolve until a new commit is pushed or the change is marked ready for review again. For more guidance, visit Writing a golden file test for Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
…/gradle_lock_files#test_changes
…files#test_changes
…sk instead of creating a new task
…ges' into feat/gradle_lock_files#test_changes
…sk instead of creating a new task
…sk instead of creating a new task
…sk instead of creating a new task
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
This commit checks if there have been any changes to the gradle files and if gradle lock files need updating. If so, it will alert then PR owner to update their PR with the new gradle lock file.s
Fixes #163228
Example test run: https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8712427303492230593/+/u/run_gradle_java8_compile_test/stdout?format=raw
This was added as an existing test under Linux gradle_java8_compile_test because benchmarking results showed on average about 3min 30s to run on my local M2 Mac. SInce it is not > 10min to run, placing it inside an existing test case was ideal.
Pre-launch Checklist
///
).If you need help, consider asking for advice on the #hackers-new channel on Discord.