You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our Kotlin project, detekt plugin writes some messages to stderr, but build completes successfully (i.e. gradle finishes with status 0; there is an opened issue on side of detekt to suppress these unnecessary messages).
However, gradle-cache-action consideres these messages to be actual errors, because they match JAVA_ERROR pattern in GradleOutErrorCollector, and fails the step.
I think this behavior should need explicit opt-in (e.g. a configuration option in action's yaml config), or more explicitly state that an error has been produced by this action.
The text was updated successfully, but these errors were encountered:
Example can be found here: https://github.com/cqfn/save/actions/runs/857338267
In our Kotlin project,
detekt
plugin writes some messages to stderr, but build completes successfully (i.e. gradle finishes with status 0; there is an opened issue on side of detekt to suppress these unnecessary messages).However,
gradle-cache-action
consideres these messages to be actual errors, because they matchJAVA_ERROR
pattern inGradleOutErrorCollector
, and fails the step.I think this behavior should need explicit opt-in (e.g. a configuration option in action's yaml config), or more explicitly state that an error has been produced by this action.
The text was updated successfully, but these errors were encountered: