Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 2.6
-
Fix Version/s: 2.7
-
Component/s: None
-
Labels:None
-
Environment:Maven 2.2.1
-
Complexity:Intermediate
-
Number of attachments :
Description
Since update to Surefire 2.6 our CI server is breaking builds every now and then with:
...
Results :
Tests run: 42, Failures: 0, Errors: 0, Skipped: 0
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error while executing forked tests.; nested exception is org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineException: Error inside systemErr parser
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
...
Up to now I was not able to reproduce the issue. It looks like a concurrency issue.
Configuration:
<configuration>
<systemPropertyVariables>
<net.sourceforge.cobertura.datafile>target/cobertura/cobertura.ser</net.sourceforge.cobertura.datafile>
<java.awt.headless>true</java.awt.headless>
</systemPropertyVariables>
<redirectTestOutputToFile>true</redirectTestOutputToFile>
</configuration>
Probably due to 42 tests ![]()
Issue Links
- is related to
-
PLXUTILS-131
Improper exception handling in executeCommandLine
-
-
SUREFIRE-639
Error inside systemOut parser: java.lang.IllegalStateException: testSetStarting called twice
-
As far as I understand this issue has been hidden by the incorrect error handling in plexus-utils, which was fixed in
PLXUTILS-131. I see a clear concurrency problem that should only be visible when redirectTestOutputToFile is true. Could you verify that the problem goes away if you disable this feature ?