François LEIBER created SUREFIRE-837:
----------------------------------------
Summary: Surefire 2.12 fails after first module
Key: SUREFIRE-837
URL: https://jira.codehaus.org/browse/SUREFIRE-837
Project: Maven Surefire
Issue Type: Bug
Affects Versions: 2.12
Environment: Maven 3.0.4, surefire 2.12, JUnit 4.10, JDK1.6_30, WinXP
Reporter: François LEIBER
Attachments: surefire2.12.log
We have a big issue with surefire 2.12 (using default configuration, which
means forkMode=once): the Junit tests of the first module pass perfectly, then
we have a "Z,0,BYE!" in the log and the surefire plugin fails with:
{code}
The forked VM terminated without saying properly goodbye. VM crash or
System.exit called ?
at
org.apache.maven.plugin.surefire.booterclient.output.ForkClient.close(ForkClient.java:244)
{code}
It seems related to the following code, taken from
maven/surefire/trunk/surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java:
{code}
runSuitesInProcess( testSet, testClassLoader, startupConfiguration,
providerConfiguration );
// Say bye.
System.out.println("Z,0,BYE!");
System.out.flush();
// noinspection CallToSystemExit
System.exit( 0 );
{code}
This happens at every run, just reverting surefire to 2.11 fixes the issue. If
I use forkMode=never, it works, but our code needs a forked VM, otherwise we
have SecurityManager issues.
The surefire configuration itself is very basic:
{code}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.12</version>
<configuration>
<argLine>-Xms128m -Xmx1024m</argLine>
<includes>
<include>**/SelfHostingTests.java</include>
</includes>
</configuration>
</plugin>
{code}
Attached is the full build log with -X.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
