"Coverage generation minion exited abnormally" with JUnit 5.8.0-RC1, not with M1

I’ve got a project (non-disclosable) using JUnit 5.8.0-M1, and when trying to bump to 5.8.0-RC1, the coverage minions fail. I’ve tested this on JDK 8, 11 and 15.

This is the difference in the --classPath (< is working, > is failing):

< /Users/user/.gradle/caches/modules-2/files-2.1/org.junit.platform/junit-platform-engine/1.8.0-M1/ec6b09bebb1f08ab88ac3067e84a2c37abac0f47/junit-platform-engine-1.8.0-M1.jar
< /Users/user/.gradle/caches/modules-2/files-2.1/org.junit.platform/junit-platform-commons/1.8.0-M1/606bc745051c0c2a608700d91a40d8a94698cdab/junit-platform-commons-1.8.0-M1.jar
< /Users/user/.gradle/caches/modules-2/files-2.1/org.junit.jupiter/junit-jupiter-engine/5.8.0-M1/7c9a3128baf19144a4dceb1d02e697384db8b2b4/junit-jupiter-engine-5.8.0-M1.jar
< /Users/user/.gradle/caches/modules-2/files-2.1/org.junit.jupiter/junit-jupiter-api/5.8.0-M1/6d6a0e5ee7373eaebba6a7357c36a468e490b47b/junit-jupiter-api-5.8.0-M1.jar
---
> /Users/user/.gradle/caches/modules-2/files-2.1/org.junit.platform/junit-platform-engine/1.8.0-RC1/4b199e46e07d8952a45fea4467fe2db67dc5e361/junit-platform-engine-1.8.0-RC1.jar
> /Users/user/.gradle/caches/modules-2/files-2.1/org.junit.platform/junit-platform-commons/1.8.0-RC1/c36e4083646b9d430f4b9d0f1a9deb12bba80093/junit-platform-commons-1.8.0-RC1.jar
> /Users/user/.gradle/caches/modules-2/files-2.1/org.junit.jupiter/junit-jupiter-engine/5.8.0-RC1/426e55d4724bff375f99e64dad52d6e37d58e2af/junit-jupiter-engine-5.8.0-RC1.jar
> /Users/user/.gradle/caches/modules-2/files-2.1/org.junit.jupiter/junit-jupiter-api/5.8.0-RC1/6f4cde27132d619d459dd0d98a1f37b35f4b6b21/junit-jupiter-api-5.8.0-RC1.jar
56,58d55
< /Users/user/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-jdk8/1.4.20/756521338269950c2a276f1abe6fef8e1a5e5528/kotlin-stdlib-jdk8-1.4.20.jar
< /Users/user/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-jdk7/1.4.20/9de2c79e95d4b4699a455e88ba285a95352e0bea/kotlin-stdlib-jdk7-1.4.20.jar
< /Users/user/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.5.30-RC/dd23741884d3d030f21cc9db12936a2690b322e0/kotlin-stdlib-1.5.30-RC.jar
65d61
< /Users/user/.gradle/caches/modules-2/files-2.1/org.apiguardian/apiguardian-api/1.1.1/7ea550039f115fcc40990925490b8ebd4b93024a/apiguardian-api-1.1.1.jar
68,69d63
< /Users/user/.gradle/caches/modules-2/files-2.1/org.jetbrains/annotations/13.0/919f0dfe192fb4e063e7dacadee7f8bb9a2672a9/annotations-13.0.jar
< /Users/user/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-common/1.5.30-RC/a85b7cb33ad571a90ba625845a9a554dae22ee33/kotlin-stdlib-common-1.5.30-RC.jar

Please let me know if I can provide more data.

[hcoles]

@davidburstrom

A new release of the plugin has now been pushed out, built against JUnit Platform 1.8.0.

I’ve not had time to dig into what’s happening on the classpath of the plugin, but agree that it ought to be possible to switch the scope of the platform dependency to ‘provided’ and pull the current version from the classpath. This may be trivially straight forward, or plagued with issues (as I said, I’ve not had chance to look). If you have time, I’d be more than happy to accept a pull request over at

https://github.com/pitest/pitest-junit5-plugin

Although it’s possible that any implementation might spill over into this repo if it involves pulling classpath items from new locations.

[hcoles]

@CasperNLD There are no known issues with the junit 5 plugin at the moment. Make sure your plugin version is compatible with your junit version.

From the plugin readme

• 1.1.0 requires pitest 1.9.0 or above and JUnit Platform 1.9.x (Jupiter 5.9.1)
• 1.0.0 requires pitest 1.9.0 or above and JUnit Platform 1.8.x (Jupiter 5.8.0)