Error while watching child process... "org.pitest.PitError: null" with JDK7

[Andrew Regan]

Hi there,

I'm getting the following failure while calculating coverage for a new project, on a Mac with JDK 7, with both 0.29 and 0.30:

[...]

12:50:26 PIT >> FINE : System class path is /usr/share/maven/boot/plexus-classworlds-2.4.jar

12:50:26 PIT >> FINE : Maxmium available memory is 910 mb

12:50:26 PIT >> FINE : using port 8092

12:50:26 PIT >> FINE : SLAVE : Installing PIT agent

12:50:26 PIT >> INFO : Sending 29 test classes to slave

12:50:26 PIT >> INFO : Sent tests to slave

12:50:27 PIT >> WARNING : Error while watching child process

java.util.concurrent.ExecutionException: org.pitest.PitError: null

Please copy and paste the information and the complete stacktrace below when reporting an issue

VM : Java HotSpot(TM) 64-Bit Server VM

Vendor : Oracle Corporation

Version : 24.0-b28

Uptime : 17588

Input -> 

 1 : -Xmx1024m

 2 : -XX:MaxPermSize=256m

 3 : -Dclassworlds.conf=/usr/share/maven/bin/m2.conf

 4 : -Dmaven.home=/usr/share/maven

BootClassPathSupported : true

at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:252)

at java.util.concurrent.FutureTask.get(FutureTask.java:111)

at org.pitest.util.CommunicationThread.waitToFinish(CommunicationThread.java:60)

at org.pitest.coverage.execute.CoverageProcess.waitToDie(CoverageProcess.java:34)

at org.pitest.coverage.DefaultCoverageGenerator.gatherCoverageData(DefaultCoverageGenerator.java:129)

at org.pitest.coverage.DefaultCoverageGenerator.calculateCoverage(DefaultCoverageGenerator.java:83)

at org.pitest.coverage.DefaultCoverageGenerator.calculateCoverage(DefaultCoverageGenerator.java:47)

at org.pitest.mutationtest.MutationCoverage.runReport(MutationCoverage.java:113)

at org.pitest.maven.RunPitStrategy.execute(RunPitStrategy.java:94)

at org.pitest.maven.PitMojo.analyse(PitMojo.java:276)

at org.pitest.maven.PitMojo.execute(PitMojo.java:254)

at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)

at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)

at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:601)

at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)

at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)

at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)

Caused by: org.pitest.PitError: null

Please copy and paste the information and the complete stacktrace below when reporting an issue

VM : Java HotSpot(TM) 64-Bit Server VM

Vendor : Oracle Corporation

Version : 24.0-b28

Uptime : 17588

Input -> 

 1 : -Xmx1024m

 2 : -XX:MaxPermSize=256m

 3 : -Dclassworlds.conf=/usr/share/maven/bin/m2.conf

 4 : -Dmaven.home=/usr/share/maven

BootClassPathSupported : true

at org.pitest.util.Unchecked.translateCheckedException(Unchecked.java:22)

at org.pitest.util.SafeDataInputStream.readByte(SafeDataInputStream.java:67)

at org.pitest.util.SocketReadingCallable.receiveResults(SocketReadingCallable.java:64)

at org.pitest.util.SocketReadingCallable.call(SocketReadingCallable.java:37)

at org.pitest.util.SocketReadingCallable.call(SocketReadingCallable.java:13)

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)

at java.util.concurrent.FutureTask.run(FutureTask.java:166)

at java.lang.Thread.run(Thread.java:722)

Caused by: java.io.EOFException

at java.io.DataInputStream.readByte(DataInputStream.java:267)

at org.pitest.util.SafeDataInputStream.readByte(SafeDataInputStream.java:65)

... 6 more

12:50:27 PIT >> INFO : Calculated coverage in 0 seconds.

... any suggestions?

[henry]

Can you post the pit section of your pom?

Thanks

Henry

[Andrew Regan]

Sure, it's just:

<plugin>

<groupId>org.pitest</groupId>

<artifactId>pitest-maven</artifactId>

<version>0.30</version>

<configuration>

<verbose>true</verbose>

<failWhenNoMutations>false</failWhenNoMutations>

</configuration>

</plugin>

... I should say that this only happens on some modules (the above config lives in a parent POM), but I haven't been able to work out what's different about those ones.

[henry]

What version of JUnit / TestNG are you using?

Thanks

Henry

[Andrew Regan]

Looks like the classpath contains junit-3.8.2 (hmm), junit-dep-4.8.2, and testng-6.8...

--
You received this message because you are subscribed to a topic in the Google Groups "PIT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pitusers/bmlrQZ5Azr4/unsubscribe?hl=en-US.
To unsubscribe from this group and all its topics, send an email to pitusers+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[henry]

This might be the cause of the problem.

PIT supports JUnit >= 4.6 only - if it's picking up 3.8.2 on the classpath this will cause an error.

The build currently tests against with testng 6.1.1. There are no known issues with 6.8 but that might be because it hasn't been tested with it . . .

[Andrew Regan]

Thanks, that fixed it: DbUnit was pulling in the old JUnit 3.8 alongside our existing JUnit 4.x