You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org> on 2010/08/21 12:42:32 UTC
[jira] Commented: (SUREFIRE-640)
org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineException:
Error inside systemErr parser
[ http://jira.codehaus.org/browse/SUREFIRE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232673#action_232673 ]
Kristian Rosenvold commented on SUREFIRE-640:
---------------------------------------------
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 ?
> org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineException: Error inside systemErr parser
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-640
> URL: http://jira.codehaus.org/browse/SUREFIRE-640
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.6
> Environment: Maven 2.2.1
> Reporter: Michael Hinterseher
> Priority: Minor
>
> 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 ;-)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira