Coverage generation minion exited abnormally! (UNKNOWN_ERROR) (with JUnit upgraded from 5.11.4 to 5.12.0)

[pzygielo]

In project using org.pitest:pitest-maven:1.18.2, on JUnit upgrade from 5.11.4 to 5.12.0, following is reported:

[ERROR] Failed to execute goal org.pitest:pitest-maven:1.18.2:mutationCoverage (default) on project XXX: Execution default of goal org.pitest:pitest-maven:1.18.2:mutationCoverage failed: Coverage generation minion exited abnormally! (UNKNOWN_ERROR)
[ERROR] 
[ERROR] Please copy and paste the information and the complete stacktrace below when reporting an issue
[ERROR] VM : OpenJDK 64-Bit Server VM
[ERROR] Vendor : Eclipse Adoptium
[ERROR] Version : 21.0.6+7-LTS
[ERROR] Uptime : 16029
[ERROR] Input -> 
[ERROR]  1 : -Daether.named.diagnostic.enabled=true
[ERROR]  2 : --add-opens=java.base/sun.nio.ch=ALL-UNNAMED
[ERROR]  3 : --add-opens=java.base/java.io=ALL-UNNAMED
[ERROR]  4 : -Dclassworlds.conf=XXX/.m2/wrapper/dists/apache-maven-3.9.9/3477a4f1/bin/m2.conf
[ERROR]  5 : -Dmaven.home=XXX/.m2/wrapper/dists/apache-maven-3.9.9/3477a4f1
[ERROR]  6 : -Dlibrary.jansi.path=XXX/.m2/wrapper/dists/apache-maven-3.9.9/3477a4f1/lib/jansi-native
[ERROR]  7 : -Dmaven.multiModuleProjectDirectory=XXX
[ERROR] BootClassPathSupported : false
[ERROR] 
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:333)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
    at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
    at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
    at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
    at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:103)
    at java.lang.reflect.Method.invoke (Method.java:580)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:255)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:201)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:361)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:314)
Caused by: org.pitest.util.PitError: Coverage generation minion exited abnormally! (UNKNOWN_ERROR)
...
    at org.pitest.coverage.execute.DefaultCoverageGenerator.gatherCoverageData (DefaultCoverageGenerator.java:157)
    at org.pitest.coverage.execute.DefaultCoverageGenerator.calculateCoverage (DefaultCoverageGenerator.java:101)
    at org.pitest.coverage.execute.DefaultCoverageGenerator.calculateCoverage (DefaultCoverageGenerator.java:53)
    at org.pitest.mutationtest.tooling.MutationCoverage.runAnalysis (MutationCoverage.java:158)
    at org.pitest.mutationtest.tooling.MutationCoverage.runReport (MutationCoverage.java:145)
    at org.pitest.mutationtest.tooling.EntryPoint.execute (EntryPoint.java:137)
    at org.pitest.mutationtest.tooling.EntryPoint.execute (EntryPoint.java:64)
    at org.pitest.maven.RunPitStrategy.execute (RunPitStrategy.java:35)
    at org.pitest.maven.PitMojo.analyse (PitMojo.java:581)
    at org.pitest.maven.PitMojo.execute (PitMojo.java:485)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:328)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
    at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
    at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
    at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
    at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:103)
    at java.lang.reflect.Method.invoke (Method.java:580)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:255)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:201)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:361)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:314)

[hcoles]

Thanks for the report. For some reason the auto resolving of platform launcher doesn't seem to be working for platform 1.12 (although the logs suggest it is being correctly added to the classpath).

Adding

            <dependency>
              <groupId>org.junit.platform</groupId>
              <artifactId>junit-platform-launcher</artifactId>
              <version>1.12.0</version>
            </dependency>

To pitest's classpath seems to work around the issue.

[pzygielo]

Thank you for checking.

I confirm that with junit-platform-launcher added all is fine again.

This seems to be similar to:

• Plugin crashes when junit-jupiter-engine dependency is not explicitly declared pitest/pitest-junit5-plugin#105.

[hcoles]

Tracked this down to an issue in the junit-5 plugin. A conflicting version of platform-launcher was being included as a transitive dependency.

pitest/pitest-junit5-plugin#109

[pzygielo]

I do confirm that with Bump org.pitest:pitest-junit5-plugin from 1.2.1 to 1.2.2 and explicit junit-platform-launcher dependency removed -- all is fine again. Thanks.