-
Notifications
You must be signed in to change notification settings - Fork 29.7k
integration_test: migrate to build.gradle.kts #156291
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
integration_test: migrate to build.gradle.kts #156291
Conversation
|
I made a mistake with the previous PR #154125 - I reverted it before letting all CI to finish running. So now I know this causes tree to break, but I don't really know much more. dashboard link I'm thinking of merging it, letting it run to the finish (likely marking the tree red), then reverting and knowing what exactly fails, submit the final version. |
|
I am about to head to vacation. @gmackall will need to make this decision. |
|
The tests should still run after the revert. The postsubmits will generally all run, regardless of future commits (unlike presubmits which cancel when you push a new commit) |
|
Thanks for explaining @gmackall. In that case, all of the the failing postsubmit tests for the previous version of this PR (#154125) appear to be flakes. I'm curious wdyt and what course of action would you suggest me to take |
Sorry for the late reply - if all the post submit failures were flakes (which they do look like at first glance to me) then I would just reland the original pr with no changes |
|
thanks @gmackall let's do this then |
After this PR is merged, all of `integration_test` Android gradle buildscripts will be in Kotlin. Follow-up of #156291 Part of ongoing effort to use Gradle Kotlin DSL a bit more ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing.
…157193) After this PR is merged, all of `integration_test` Android gradle buildscripts will be in Kotlin. Follow-up of flutter#156291 Part of ongoing effort to use Gradle Kotlin DSL a bit more ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing.
This PR is yet another attempt (after #154125) to reland #142008.
Benefit: this will be the first plugin in Flutter repo that uses Gradle KTS for Android buildscripts. Once it works fine, we can follow up with migration of more plugins later.
The previous error message was:
The
integration_testplugin now putscom.android.tools.build:gradle:8.1.0on its classpath since #153795.This makes me take an optimistic bet that it won't kill the autoroller now 🤞
Pre-launch Checklist
///).If you need help, consider asking for advice on the #hackers-new channel on Discord.