Upgrading Gradle to 7.3 causes build failure in the test logger plugin #241
Comments
|
To be honest, I don't know if this is actually valid. My builds start to misbehave after I upgraded, but even downgrading back to 7.2 and 6.9.1 gave me the exact same issue. After many cleans the build suddenly worked again. Let's just leave this as a non-issue. |
|
Works for me too. It might have been a rogue daemon. |
|
After some more research I'm pretty sure it isn't a rogue daemon. After stopping all with both |
|
That's interesting. Anyway I will keep an eye out for it too. I've upgraded a few of my projects at work to use this version of the plugin already and so far yet to see this issue. It could be related to this - https://discuss.gradle.org/t/my-plugin-cant-be-applied-when-plugin-is-built-with-gradle-7-1-1/40464 "A plugin built on Gradle 7 can't be used on Gradle 6" but yet to be verified. In any case, I don't intend to re-build the plugin using Gradle 6. |
|
Hey guys, I am having the same issue. I am actually using Gradle 6.9.1 but I am not able to use test logger 3.1.0. |
|
I have same issue on projects with Kotlin Multiplatform + Gradle 7.2 |
|
Hmm that's interesting. We need to get to the bottom of this. |
|
We have the issue described in the initial post after upgrading from 3.0.0 to 3.1.0. Gradle 6.9.1 |
|
I can understand why 3.1.0 might not work on Gradle 6.x due to Groovy version differences but it's quite odd that it wouldn't work on some builds that use Gradle 7.x. |
|
Same here with Gradle 6.9.2 and upgrading 3.0.0 -> 3.1.0: |
|
I'm hitting the same issue with version 3.2.0 and Gradle 7.4, and java 11. |
|
Same issue (Receiver class com.adarshr.gradle.testlogger.logger.ParallelTestLogger does not define or inherit an implementation of the resolved method 'abstract java.lang.Object getProperty(java.lang.String)' of interface groovy.lang.GroovyObject.) with 3.1.0 and Gradle version 6.6 and Java 11. For now, pinned to 3.0.0 which seems to work fine, so I guess some bump in there broke compatibility? Intentionally? |
|
This is really worrying. By the way, 3.2.0 doesn't address this issue. In 3.1.0, the Gradle version was upgraded from 6.x to 7.x. So that means it's now built using Groovy 3.0. Perhaps this has some connection with the errors you are seeing. If anyone could provide me an MVCE, it will be an immense help. I'm asking because we use the same version of the plugin in hundreds of places in the place where I work and no one has reported this issue yet. |
|
By the way, just to be clear, we cannot support Gradle < 7 for plugin version > 3.1.0. Sorry. This is because of gradle/gradle#18570. If anyone is facing the same error on Gradle >= 7 AND plugin version >= 3.1.0, please create a reproducible sample. |
|
Aha, ok, that was not clear for me so thanks for the clarification. We'll look into a Gradle upgrade on our end then 👍 |
Description
After upgrading Gradle to 7.3 it's no longer possible to use the plugin, because the build fails with the following message:
Versions
3.1.07.311Type of test being run
This was ran with JUnit, but it fails on each test.
Test logger configuration
No custom configuration
Additional information
The (near) complete stack trace:
The text was updated successfully, but these errors were encountered: