You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Chad Wilson (JIRA)" <ji...@codehaus.org> on 2011/05/20 03:56:22 UTC
[jira] Created: (SUREFIRE-741) Stdout/stderr is now not being
included in XML test reports for test failures
Stdout/stderr is now not being included in XML test reports for test failures
-----------------------------------------------------------------------------
Key: SUREFIRE-741
URL: http://jira.codehaus.org/browse/SUREFIRE-741
Project: Maven Surefire
Issue Type: Bug
Components: Maven Failsafe Plugin, Maven Surefire Plugin
Affects Versions: 2.8.1, 2.8
Reporter: Chad Wilson
In Surefire 2.8 and 2.8.1 there is no std-out and std-err being included in test reports for either the Surefire or Failsafe plugins. This means that tools like TeamCity cannot provide you with the associated test logging alongside your stacktrace when a test fails, making debugging on large CI builds very difficult.
This appears to be caused inadvertently by some changes related to SUREFIRE-732.
--
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
[jira] Commented: (SUREFIRE-741) Stdout/stderr is now not being
included in XML test reports for test failures
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267526#action_267526 ]
Kristian Rosenvold commented on SUREFIRE-741:
---------------------------------------------
To be correct, the problem was *fixed* with commits from SUREFIRE-732, but I was not aware of the problem. So I added an IT r1125083. It broke in 2.8.
> Stdout/stderr is now not being included in XML test reports for test failures
> -----------------------------------------------------------------------------
>
> Key: SUREFIRE-741
> URL: http://jira.codehaus.org/browse/SUREFIRE-741
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
> Affects Versions: 2.8, 2.8.1
> Reporter: Chad Wilson
> Fix For: 2.9
>
>
> In Surefire 2.8 and 2.8.1 there is no std-out and std-err being included in test reports for either the Surefire or Failsafe plugins. This means that tools like TeamCity cannot provide you with the associated test logging alongside your stacktrace when a test fails, making debugging on large CI builds very difficult.
> This appears to be caused inadvertently by some changes related to SUREFIRE-732.
--
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
[jira] Closed: (SUREFIRE-741) Stdout/stderr is now not being
included in XML test reports for test failures
Posted by "Chad Wilson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chad Wilson closed SUREFIRE-741.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.9
I have tested this in 2.8.2-SNAPSHOT (now 2.9-SNAPSHOT) and the behaviour has been restored. Also, see Kristian's comment on SUREFIRE-704.
> Stdout/stderr is now not being included in XML test reports for test failures
> -----------------------------------------------------------------------------
>
> Key: SUREFIRE-741
> URL: http://jira.codehaus.org/browse/SUREFIRE-741
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
> Affects Versions: 2.8, 2.8.1
> Reporter: Chad Wilson
> Fix For: 2.9
>
>
> In Surefire 2.8 and 2.8.1 there is no std-out and std-err being included in test reports for either the Surefire or Failsafe plugins. This means that tools like TeamCity cannot provide you with the associated test logging alongside your stacktrace when a test fails, making debugging on large CI builds very difficult.
> This appears to be caused inadvertently by some changes related to SUREFIRE-732.
--
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
[jira] Commented: (SUREFIRE-741) Stdout/stderr is now not being
included in XML test reports for test failures
Posted by "Chad Wilson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=267527#action_267527 ]
Chad Wilson commented on SUREFIRE-741:
--------------------------------------
Ah okay, I misunderstood. Thanks for clearing that up :-)
> Stdout/stderr is now not being included in XML test reports for test failures
> -----------------------------------------------------------------------------
>
> Key: SUREFIRE-741
> URL: http://jira.codehaus.org/browse/SUREFIRE-741
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
> Affects Versions: 2.8, 2.8.1
> Reporter: Chad Wilson
> Fix For: 2.9
>
>
> In Surefire 2.8 and 2.8.1 there is no std-out and std-err being included in test reports for either the Surefire or Failsafe plugins. This means that tools like TeamCity cannot provide you with the associated test logging alongside your stacktrace when a test fails, making debugging on large CI builds very difficult.
> This appears to be caused inadvertently by some changes related to SUREFIRE-732.
--
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