-
Notifications
You must be signed in to change notification settings - Fork 28.7k
Update outdated runners in the benchmarks folder #91126
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
Update outdated runners in the benchmarks folder #91126
Conversation
ab61685
to
4b60e29
Compare
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. |
test-exempt: refactor with no semantic change (applying new boilerplate) |
repositories { | ||
google() | ||
mavenCentral() | ||
} | ||
|
||
dependencies { | ||
classpath 'com.android.tools.build:gradle:7.0.0' | ||
classpath 'com.android.tools.build:gradle:4.1.0' |
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.
I think this was intentionally migrated to Gradle 7.0.0. This change may conflict with #90642
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.
Ahh, OK, I'll revert this. Is someone migrating the template too?
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.
yep. #90642 migrates templates too
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.
Actually, I think I'll wait for #90642 to land, and then update this and the other PR. It's likely to conflict in other ways too, and I don't want make Taha have to merge even more files.
@@ -2,25 +2,17 @@ | |||
// Use of this source code is governed by a BSD-style license that can be | |||
// found in the LICENSE file. | |||
|
|||
// This file is auto generated. | |||
// To update all the build.gradle files in the Flutter repo, | |||
// See dev/tools/bin/generate_gradle_lockfiles.dart. |
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.
nit: this file is auto-generated
@@ -2,14 +2,8 @@ | |||
// Use of this source code is governed by a BSD-style license that can be | |||
// found in the LICENSE file. | |||
|
|||
// This file is auto generated. | |||
// To update all the settings.gradle files in the Flutter repo, | |||
// See dev/tools/bin/generate_gradle_lockfiles.dart. |
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.
ditto
Thinking this through, I wonder if we should have a more general purpose script that keeps the boilerplate in sync. Potentially, the new script could run |
I think that's an excellent idea. |
In doing this, I found there were a few directories that needed to be exempt (there's a test for the outdated embeddings, and there's an android test where it has a custom runner, for instance), but in general I think that should be possible. My basic methodology was to remove all of the boilerplate directories entirely, and then regenerate using |
got it. We don't have a well defined pattern for testing older project files, or even showing good error messages in the tool when the current project files are out-dated. |
Once we have a migration script, we could have a CI test that runs the script and sees if there is any difference, though. That would at least catch the runners that are out of date in the repo when we update the templates. |
4b60e29
to
e20feec
Compare
Even if we just ran |
d076fff
to
54c8af9
Compare
@blasten OK, I think I've merged this with #90642 now, and I re-ran the |
54c8af9
to
71c668f
Compare
This pull request is not suitable for automatic merging in its current state.
|
This change updates the platform runners in the benchmarks subdir. I've attempted to replace the entire group with new code as if the project were recreated with flutter create so that they don't become a Frankenstein of minor changes to make it work again, but just plain old generated code that can be replaced and updated in place.
…)" (flutter#92106) This reverts commit 31e3364.
)" (flutter#92106)" This reverts commit b412f6f.
…utter#91126)" (flutter#92535)" (flutter#93323) This reverts commit bfe9c59.
Description
This PR updates the platform runners in the benchmarks subdir.
I've attempted to replace the entire group with new code as if the project were recreated with
flutter create
so that they don't become a Frankenstein of minor changes to make it work again, but just plain old generated code that can be replaced and updated in place.Tests