This message was deleted.
# cachings
Slackbot
08/10/2023, 9:30 AMThis message was deleted.
v
Vampire
08/10/2023, 9:40 AMThat's a pretty bad idea actually.
You are now saying that the outputs are up to date, no matter what they contain, they just need to exist.
So if you for example manually change the output files, the task will no longer be out-of-date.
Vampire
08/10/2023, 9:43 AMIf the output files are not present, the task should indeed be out-of-date of course.
Sometimes I have seen that up-to-dateness state got corrupted and tasks were considered up-to-date when they shouldn't.
I didn't yet investigate too deep, but when it happened needed to get it going fast.
So I deleted
<rootproject>/.gradle<GRADLE_USER_HOME>~/.gradlegradle.propertiesinit.dm
Mattia
08/10/2023, 9:52 AMThanks Vampire! So you believe it’s a corruption problem, rather than the task being misconfigured? Trying to understand whether I should report a bug to the task owners or not. I think for example one could define a task with an output, but then don’t write to it in some conditions, also forget to add these conditions to the task inputs. In this case the UP-TO-DATE evaluation would be correct?
v
Vampire
08/10/2023, 10:13 AMI'm afraid I didn't understand your last sentence fully.
Iirc, a task that does not have output files can never be up-to-date.
Unless manually configured so with
outputs.upToDateWhen { ... }