Justin Breitfeller
10/20/2022, 4:42 PMAppending input file fingerprints for 'inputArtifact' to build cache key: 3447d06a1cf0b5b0770a5a19c48d6c16 - NAME_ONLY{/Users/justinbreitfeller/.gradle/caches/modules-2/files-2.1/com.android.tools.build/aapt2/7.3.1-8691043/318150c1078be0bd4bdff348e6d79b8ab7991653/aapt2-7.3.1-8691043-osx.jar='aapt2-7.3.1-8691043-osx.jar' / 4341034cb2e00bae6db6d9e642ab5c12}
On my remote machine
Appending input file fingerprints for 'inputArtifact' to build cache key: 0df6c43612fd0d3d6d0860576053d155 - NAME_ONLY{/home/circleci/.gradle/caches/modules-2/files-2.1/com.android.tools.build/aapt2/7.3.1-8691043/41177c11a257af096624e80d433714aae61ca9f6/aapt2-7.3.1-8691043-linux.jar='aapt2-7.3.1-8691043-linux.jar' / 25f9626e6fddbffaa42760fb2c950d38}
Am I wrong to assume that this NAME_ONLY inputArtifact won’t help cross platform since the JAR files have the platform in its name?Doni
10/27/2022, 11:18 AMSergey Chelombitko
10/31/2022, 3:57 PMŁukasz Wasylkowski
11/01/2022, 9:08 PMClass path of task '...' has changed from xxx to yyy
? I see it happen for modules with very few dependencies when I change a completely unrelated build.gradle
file (one that the offending module doesn’t depend on). Build scan doesn’t seem too helpful here sadlyEl Zhang
11/02/2022, 3:23 AMinputChanges.getFileChanges(...)
with ListProperty<Directory>
? Should I convert it to ConfigurableFileCollection
or is there any other ways can help me keep the ListProperty<Directory>
property type which is more clear to be used?
According to the doc:
…be it of type,RegularFileProperty
orDirectoryProperty
ConfigurableFileCollection
Alex Spence
11/02/2022, 10:39 PMorg.gradle.internal.execution.OutputSnapshotter$OutputFileSnapshottingException: Cannot snapshot output property 'outputDirectory'.
java.io.UncheckedIOException: Failed to create MD5 hash for file '/Users/spence/.gradle/caches/transforms-3/b857c89a93e3ad26d7a3a2df48b5cb23/transformed/unzipped-distribution/gradle-7.5.1/subprojects/docs/src/snippets/antMigration/fileDeps/kotlin/libs/log4j-1.2.8.jar' as it does not exist.
Zak Taccardi
11/03/2022, 8:24 PMBrian Stewart
11/10/2022, 2:47 AMDoni
11/11/2022, 9:05 AMJakub Mosakowski
11/16/2022, 9:14 AMSebastian Kacprzak
11/21/2022, 11:51 AMEduard-Cristian Boloș
11/22/2022, 1:57 PMEduard-Cristian Boloș
11/23/2022, 12:28 PMritesh singh
11/28/2022, 10:54 PMbuild cache overhead
shows 2hrs - it took only max 45 minutes after running these commands
• rm -rf ~/.gradle/cache/build-cache-*
• ./gradlew clean
• ./gradlew assembleDebugFrancesco Bonnì
11/29/2022, 7:21 PMRoded Bahat
12/20/2022, 6:02 AM-Dorg.gradle.caching.debug=true
I can see that two invocations of the task are processing the same files, each with an identical fingerprint between executions.
However, Appending input file fingerprints for '$1' to build cache key
still outputs a different fingerprint per execution.
Any idea how I can debug this further?
The tarred file paths are not considered for fingerprinting right?
I can attach the logs as well, though they might be largish.
Thanks
Tar task:
task srcTar(type: Tar) {
inputs.files(project.fileTree(".") {
include "src/main/**"
})
outputs.file(includesTarFile)
outputs.cacheIf { true }
from projectDir
getArchiveFileName().set(tarArchiveFileName)
include "src/**/*"
}
(Gradle 7.6).AG
01/09/2023, 6:03 PMbuild-logic-settings
included build in my pluginManagement
block and I have a convention plugin to configure the build cache inside the project, as I understand from the docs
This configuration precedence does not apply to plugin builds included through pluginManagement as these are loaded before the cache configuration itself.
cache config wont work for build-logic-settings
, so as a workaround I've applied that plugin directly in build-logic-settings
apply(from = "cache-plugin/src/main/kotlin/convention-cache.settings.gradle.kts")
but after generating a build scan it says that
The build cache configuration of the root build differs from the build cache configuration of the early evaluated ':build-logic-settings' included build
so what's the right way to have the same build cache config?AG
01/10/2023, 4:16 PMgradleEnterprise.buildCache
remote(gradleEnterprise.buildCache) {
isEnabled = true
isPush = isCI
}
in the included build that is inside pluginManagement
block?
I've tried copy-pasting the same config in my included build but got this error
A problem occurred configuring project ':build-logic-settings'.
Could not create service of type BuildCacheController using .createBuildCacheController().
java.lang.UnsupportedOperationException (no error message)
Ronanb Browne
02/01/2023, 6:23 PMDmitriy Voronin
02/03/2023, 6:59 PMcom.android.build.gradle.internal.tasks.DexMergingTask
It's incremental, but i thought it shouldn't affect fingerprinting.
How to debug it further?Jan Duzinkiewicz
02/15/2023, 7:43 PMJan Duzinkiewicz
02/15/2023, 7:55 PMEug
02/20/2023, 4:32 PMGianfranco Monzon
02/21/2023, 12:13 AMCould not load entry d6d33e5606c65e111f4e29d41ec49a57 from remote build cache: Premature end of Content-Length delimited message body (expected: 12,061,751; received: 1,543,568)
Gabriel Feo
02/28/2023, 3:42 PMDmitriy Voronin
03/01/2023, 12:26 PMOverlapping outputs: Gradle does not know how file 'build/roomSchemas/kaptDebugKotlin' was created (output property 'annotationProcessorOptionProviders.$0.$1.effectiveSchemaLocationDir'). Task output caching requires exclusive access to output paths to guarantee correctness (i.e. multiple tasks are not allowed to produce output in the same location).
It's certainly doesn't affect every build, so I can't understand the reproducing steps for now.
I ask here, hoping it's some known issue with known workaround.
Versions:
• AGP 7.4.1
• Gradle: 7.5.1
• Cache fix plugin: 2.6.5Ronanb Browne
03/04/2023, 12:33 PMmoduleVersion
which gets set under the hood at build time it seems, this is set to the Gradle project version by default, for us that changes run to run based on a timestamp (removing the timestamp is not a option right now in our versioning schema). This moduleVersion property which dokka sets is breaking caching for us as input value "moduleVersion" is different from run to run, due to our versioning timestamp, Any examples on how i can normalize this to tell Gradle to not consider this with caching, from some googling possibly i can use this interface ?, but having trouble finding any actual examples of use.melix
03/07/2023, 2:22 PMGabriel Feo
03/08/2023, 7:24 PMcacheIf { !isCI }
but that means developers will have to build it locally, which may or may not be an issuemelix
03/15/2023, 8:41 AMmelix
03/15/2023, 8:41 AMjar
could come from, since nowhere in the build we add such a dependencyjar
is on classpath, but no explicit dependency is added: https://ge.micronaut.io/s/bzegzmbnkvpca/console-log?page=1#L13Vampire
03/15/2023, 9:34 AMgood morning (or good whatever, depending on where you are)There was a pseudo-timezone for that, but I forgot how it was called. Something like "Good GCT morning" (Global Chat Time) that you can use always if it is morning for you. 🙂
deepy
03/15/2023, 11:14 AMVampire
03/15/2023, 11:26 AMlptr
03/16/2023, 8:32 PM