This message was deleted.

Is the task maybe up-to-date locally and thus does not execute? Otherwise maybe try to publish the configuration cache report file from the CI build so that you can look at it any maybe find more information.

Actually it was reported as FROM-CACHE on the CI, and that seems extremely odd to me

:redacted:generateReleaseProto

was served

FROM-CACHE

but gave that error? o_O That sounds pretty impossible. o_O

I will check again because it sounds impossible to me as well.

Otherwise, again, the CC report might help to see where it actually happened exactly.

was served

FROM-CACHE

but gave that error?

The error can come from

onlyIf

or

doNotCacheIf

predicates which are also evaluated at execution time even if the task ends up FROM-CACHE (I don't know if this is the case for the protobuf plugin, adding just to clarify)

Checked again, the task comes

FROM-CACHE

. I have now updated to the latest protobuf gradle plugin and the error did not show up. But I will try again locally switching to version

0.9.1

and re-running the task

I also thought so and looked at the sources. At least there neither of those actions is used, which is why I advised to look at the CC report that contains a stacktrace iirc. 🙂

everything is ok locally. I have the configuration cache report from the CI machine: what should I look for?

Yeah, that is

getIsTest

which was an

@Input

up to and including 0.9.2, but was made

@Internal

with 0.9.3

@Andrea Di Menna do you have

org.gradle.configuration-cache.internal.load-after-store=false

set up somewhere by chance? The way protobuf plugin used

getProject

before the fix doesn't seem to be problematic for CC otherwise. I'm asking because it may indicate a bug in Gradle, if there's no parameter tweaking on your side.

nope, I don’t have that option set up