-
Notifications
You must be signed in to change notification settings - Fork 29.7k
more gradle upgrades #50388
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
more gradle upgrades #50388
Conversation
| zipStoreBase=GRADLE_USER_HOME | ||
| zipStorePath=wrapper/dists | ||
| distributionUrl=https\://services.gradle.org/distributions/gradle-4.10.2-all.zip | ||
| distributionUrl=https\://services.gradle.org/distributions/gradle-5.6.2-all.zip |
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.
This is the only one I'm not 100% sure about whether we should touch. This affects customers.
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.
Should we split it to another PR? WDYT @blasten?
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.
this file isn't really used. I don't think it will break customers as far as I can tell.
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. This is used if a developer tries to build the plugin alone using Android Studio. cc @gaaclarke who just had this issue. (#50480)
|
We may also want to use |
|
gonna wait for the linux tests to pass with the new docker build, but then should approve |
dev/ci/docker_linux/Dockerfile
Outdated
| RUN mkdir -p "${GRADLE_ROOT}" | ||
| ENV GRADLE_ARCHIVE="${GRADLE_ROOT}/gradle.zip" | ||
| ENV GRADLE_URL="https://services.gradle.org/distributions/gradle-4.4-bin.zip" | ||
| ENV GRADLE_URL="https://services.gradle.org/distributions/gradle-5.6.2-bin.zip" |
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.
what is this used for though? Do we have tests that call the global Gradle instead of the gradlew script?
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.
This is what gradlew will use to download the gradle we actually want.
It would be nice if gradlew was smart enough to realize your system gradle was already the right version, but either way it's easier to just find and replace these if they're all in sync. And the current version definitely has bugs around unicode handling...
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.
gradlew initializes the download of the Gradle binary based on the distributionUrl from gradle-wrapper.properties.
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.
But gradlew uses gradle to do the download :)
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.
IOW, you can't use gradlew if you don't already have gradle installed.
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.
(Which is why it would be nice if gradlew would somehow just check if your current gradle version is the same as what it's about to download)
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.
gradlew is just a script that initializes gradle-wrapper.jar. The only requirement is to have java installed.
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 hm. I thought for sure at some point it required gradle of some version to be installed first. I was either wrong or that's changed.
I'm not sure why we need this then.
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'll get rid of it and see what breaks haha
|
Probably have to sync this to head for the golden failure. |
|
Is there an introaged golden or something? |
blasten
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
|
Taking Gradle out of the Dockerfile makes me happy, LGTM. |
|
I was confusing that you need gradle to initialize the gradle wrapper, but once its initialize dyou don't need it anymore - and we just keep the initialized files checked in. |
Ah, that makes sense, since I've never had to install Gradle before Flutter. |
|
Hm. It looks like this changed 5 golden files. According to the dashboard, they have all been triaged as positive. Looks like they are all related to shadows, is this expected to change those files? |
|
No, this is changing gradle wrapper options for Android builds. This should have 0 impact on web, and 0 impact on goldens. |
|
It looks like a different one is failing each time... |
|
My assumption is that something on master has actually changed these and this patch is the first one to catch it, but that may be wrong. Perhaps I keep facing issues because it's runninginto errors sequentially and failing ont he first one? |
|
I've been approving them because they seem like minor pixel differences. |
|
Now there are 6. For some reason it looks like each re-run has failed a new golden file test. It's only happening on web... maybe @chingjun will have some insight? |
|
Talked offline and we think we figured it out. This test is updating the docker image, which may be pulling in a newer version of chrome, which means rendering differences on shadows perhaps. Unfortunately,t he test I'm running runs in a loop and is failing on the first failure and not executing the rest of the tests, so gold is only letting me triage one by one. |
|
Caught up offline, that test runs on a loop through different elevation values. A different one in each run is failing because it is throwing inside of the loop. I'm going to update the test to get it out of a loop. The cause for the change may be because we are picking up a new version of chrome. |
|
Ahh, Chrome update! I guess the web goldens will be susceptible to this every time our Docker image pulls in a new Chrome version. |
|
Ok, with the test rewritten so the loop is outside the test I was able to triage all the shadow changes at once. It should pass now. |
christopherfujino
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. Plan to hotfix this into stable.
|
Tree is not red. Merging this. |
@blasten
Fixes #50386
Fixes #50480