Róbert Papp

Don't create the hidden comment on success, that's still noise and takes up vertical space, also email notification might be sent.

Huh 👏

(I had to fix this because I was running 100s of Gradle builds in unit tests for a Gradle plugin, so it was warning and polluting my test logs.) Thanks...

We;re seeing this and the last erroring logcat is suggesting an interplay of Jacoco, Garbage Collector (finalizers) and native. It happens after ~10 minutes of successful test executions. Failure rate...

This looks like a really nice investigation and fix! 👏🏻

Probably caused by this line: https://github.com/android/android-test/commit/cfd3a9facaffd28dc074e920d533fe4283d29a41#diff-a5dff1a88413274bad1d9628465e84c19dc4ce39ede38e6eaf47467fbed707d8R406 I became aware of it from https://github.com/android/android-test/issues/1454#issuecomment-1227553260.

@MaronHatoum @chludwig-haufe I think we should merge this before making any further improvements to this page. (Which should be in scope of the PR changing the logic proposed in https://github.com/renovatebot/renovate/issues/16012).

@lptr how can a task be actually up to date and not up to date at the same time?

`setDidWork` makes things complicated, I see, thanks. > because there were no files to delete Sounds like a `NO-SOURCE` to me :)

Is there anything that can be done here? Other than maybe changing the wording?