-
Notifications
You must be signed in to change notification settings - Fork 52
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
Configuration Cache can not be used after one run #646
Labels
Comments
shanshin
added a commit
that referenced
this issue
Jun 27, 2024
Due to the fact that a file was used as task input, it was placed in the configuration cache as entry, and changing this file causes the cache invalidation. Problem in line `localArtifact.set(variant.artifactGenTask.flatMap { task -> task.artifactFile })`. flatMap function behaves strangely enough with the configuration cache, see also gradle/gradle#25645 Fixes #646
Thanks for the report and the test! |
shanshin
added a commit
that referenced
this issue
Jun 27, 2024
Due to the fact that a file was used as task input, it was placed in the configuration cache as entry, and changing this file causes the cache invalidation. Problem in line `localArtifact.set(variant.artifactGenTask.flatMap { task -> task.artifactFile })`. flatMap function behaves strangely enough with the configuration cache, see also gradle/gradle#25645 Fixes #646
shanshin
added a commit
that referenced
this issue
Jun 27, 2024
Due to the fact that a file was used as task input, it was placed in the configuration cache as entry, and changing this file causes the cache invalidation. Problem in line `localArtifact.set(variant.artifactGenTask.flatMap { task -> task.artifactFile })`. flatMap function behaves strangely enough with the configuration cache, see also gradle/gradle#25645 Fixes #646 PR #648
Fixed in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When the configuration cache is enabled, the cache entry is always immediately invalidated after the first run
Errors
If present, stacktraces or files from
build/kover/errors
directoryExpected behavior
After invoking a command once, the configuration cache from the previous invocation should be reused
Reproducer
By applying the following patch to the project you can see that the configuration cache is not used in the first identical run because the test assertion fails
In the output of this run you can see the following message
If you run the build three times, on the third attempt the configuration cache will be re-used, if you apply the patch below the test passes, but it should already be available after the first attempt.
Environment
The text was updated successfully, but these errors were encountered: