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
Build cache miss when jars have been hashed with different normalization configuration #16144
Comments
ghale
added a commit
that referenced
this issue
Feb 13, 2021
Normalization rules were not being properly captured when calculating the cache key for file hashes during runtime classpath normalization. This was causing incorrect build cache misses under the right sequence of events. Fixes #16144
ghale
added a commit
that referenced
this issue
Feb 16, 2021
Normalization rules were not being properly captured when calculating the cache key for file hashes during runtime classpath normalization. This was causing incorrect build cache misses under the right sequence of events. Fixes #16144
I created #16192 to backport the fix to 6.8.3. |
github-actions bot
pushed a commit
to w4bo/github-actions-helloworld
that referenced
this issue
Feb 23, 2021
This is a patch release for Gradle 6.8. This fixes [a critical bug](gradle/gradle#16144) present in Gradle 6.8, 6.8.1 and 6.8.2. [All issues fixed in this patch release](https://github.com/gradle/gradle/milestone/171?closed=1) Please don’t use the original 6.8 release or previous patch releases, and instead upgrade to 6.8.3. ## Upgrade Instructions Switch your build to use Gradle 6.8.3 by updating your wrapper: `./gradlew wrapper --gradle-version=6.8.3` See the [Gradle 6.x upgrade guide](https://docs.gradle.org/6.8.3/userguide/upgrading_version_6.html#changes_6.8) to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.8.3. ## Reporting Problems If you find a problem with this release, please file a bug on [GitHub Issues](https://github.com/gradle/gradle/issues) adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the [forum](https://discuss.gradle.org/c/help-discuss).
tobiasschaefer
added a commit
to camunda-community-hub/micronaut-camunda-platform-7
that referenced
this issue
Feb 23, 2021
martisaw
pushed a commit
to camunda-community-hub/micronaut-camunda-platform-7
that referenced
this issue
Feb 23, 2021
Is it really a "critical bug" as per the 6.8.3 release notes? Seems like it's only performance relevant? :) |
This can lead to incorrect builds, which makes it a critical bug. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've received multiple reports of cache misses on runtime normalization input properties for jar files that should be identical. At least one reporter confirmed that using a different gradle user home resolved the issue. It turns out some of the changes to runtime classpath normalization in 6.8 don't accurately capture changes to the normalization configuration, which can lead to a sequence of events like the following:
Expected Behavior
We should get.a build cache hit on the task.
Current Behavior
The build cache key can be incorrectly calculated on one side or the other, causing a miss.
Context
Poorer build perfomance due to cache misses.
Steps to Reproduce
See above.
The text was updated successfully, but these errors were encountered: