-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kover 0.7.6 + Jacoco: Various configuration cache problems #606
Comments
Hi, |
So, one is basically dependent on what Jacoco version the specific Gradle version ships with? Well, ok for me then, because I try to keep the Gradle version up-to-date. |
Not really, latest Kover Gradle Plugin uses JaCoCo version There is also a problem that now the tests for configuration cache support and project isolation are run only for Kover tooling ( |
Are you using Gradle |
Ok, just to get this right, would using
then already fix the issue, because kover would directly reference the build-dependent version of Jacoco? Because I just tried that out and see the same issue.
Hrm, that's an issue indeed. I don't know what the plan is in general anyways, i.e. if both toolings should be kept around forever or only until Kover gains instrumentation test support on Android. Right now I trust Jacoco a little more, because I've used it for years in my own tooling and know its quirks and things, so I'm a little hesitant to switch to Kover tooling just yet (even though I only run unit, no instrumentation tests). |
I'm using Gradle 8.7. I also have a multi-module setup and I run all tests (and coverage tasks) from the root build. But I could also reproduce it when only targeting a single module, like this:
with these
|
Closed in favour of #630 |
When Jacoco is enabled with Kover and Gradle's configuration-cache as well, I receive spurious failures like
or
When I disable Jacoco and use the built-in Intellij coverage plugin or disable the configuration cache, the errors are gone.
Environment
The text was updated successfully, but these errors were encountered: