Closed psibre closed 2 years ago
Thanks for the report I'll have a look. I think is because I wasn't expected the sessioninfo be a list but an unique item, Unfortunately the Jacoco format is not documented and had to make suppositions (especially as they don't use a <sessioninfos>
wrapper around.
As for exception I don't think that the failure of creating a report should fail the build. IMHO Is not an important information and I think JacocoReport task neither fails the build in case of error.
Wow, that was nearly instantaneous support! Thanks so much for your help!
Confirmed fixed with v1.0.1.
Thanks to your nice complete report is was easy to spot the problem, reproduce it and fix it fast 😉.
First of all, thanks for providing this plugin -- very helpful!
I've run into an issue when the JaCoCo XML report contains multiple
sessioninfo
elements at the top. This seems to occur only if the tests are run with amaxParallelForks
value greater than 1.When the tests are run with a value of 1, no error occurs.
But, for example, my
build.gradle
contains this:This results in a
jacocoTestReport.xml
that starts like this:And when I run the conversion task I get
And the expected
build/coverage.xml
is not created.Adding insult to injury, the task doesn't throw an exception, and Gradle falsely claims that the build was successful...