This message was deleted.
# develocity
s
This message was deleted.
a
some tasks are excluded from build cache using
@DisableCachingByDefault
https://docs.gradle.org/8.1.1/userguide/build_cache.html#sec:task_output_caching_disabled_by_default The message
"Not worth caching"
is manually added https://github.com/gradle/gradle/blob/2cb246e2f440911b2ca67e1bad5d81f5821a4ceb/subprojects/language-jvm/src/main/java/org/gradle/language/jvm/tasks/ProcessResources.java#L29. It’s a bit of a standard message, it’s copy and pasted in a lot of different classes.
n
This one is taking 34 seconds in our CI. Which I think has started happening recently. Seems to me that caching would have helped but I'm not sure why it has slowed down
a
fingerprinting inputs takes 19 seconds, which seems very high. Maybe a large directory or file was added as an input, and Gradle takes a long time to scan it?
n
Ok I just looked back through the history and usually it takes 12-15 seconds for this task. I guess some gremlins caused this one to be particularly slow. I’ll ignore it for now.
w
I definitely takes long, though I wonder how caching would help: These are all operations of copying files from one location to another, the build cache only would add another layer of copying around. Or does your process resources task do something CPU intensive?
n
I guess caching may not help. I guess we have slow FS in CI. I think the problem is intermittent. Will investigate and report back