You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jan Fredrik Wedén (JIRA)" <ji...@codehaus.org> on 2010/12/21 13:05:57 UTC
[jira] Created: (SUREFIRE-672) Failsafe no longer fails builds due
to broken failsafe-summary.xml file
Failsafe no longer fails builds due to broken failsafe-summary.xml file
-----------------------------------------------------------------------
Key: SUREFIRE-672
URL: http://jira.codehaus.org/browse/SUREFIRE-672
Project: Maven Surefire
Issue Type: Bug
Components: Maven Failsafe Plugin
Affects Versions: 2.7
Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr7-20100219_54049 (JIT enabled, AOT enabled)
OS name: "windows xp" version: "5.1 build 2600 service pack 3" arch: "x86" Family: "windows"
Reporter: Jan Fredrik Wedén
Priority: Blocker
Upgrading maven-failsafe-plugin from version 2.6 to 2.7 causes builds with integration test errors to be reported as successful.
>From my understanding, the failsafe verify goal uses the summary file (default: target\failsafe-reports\failsafe-summary.xml) to check whether executed integration tests passed or had any errors. I've pasted the content of this file below as it is generated by the failsafe plugin version 2.6 and 2.7 respectively for the same build with the same integration test errors. It appears that the integration-test goal does not generate this file correctly in version 2.7.
{code:title=failsafe plugin v2.6: failsafe-summary.xml|language=XML}
<?xml version="1.0" encoding="UTF-8"?>
<failsafe-summary result="255" />
{code}
{code:title=failsafe plugin v2.7: failsafe-summary.xml|language=XML}
<?xml version="1.0" encoding="UTF-8"?>
<failsafe-summary />
{code}
The result for this build is that the failsafe plugin version 2.6 fails the build (as it should) while failsafe plugin version 2.7 does not and the build is reported as successful.
--
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] Updated: (SUREFIRE-672) Failsafe no longer fails builds due
to broken failsafe-summary.xml file
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold updated SUREFIRE-672:
----------------------------------------
Fix Version/s: 2.7.1
Assignee: Kristian Rosenvold
> Failsafe no longer fails builds due to broken failsafe-summary.xml file
> -----------------------------------------------------------------------
>
> Key: SUREFIRE-672
> URL: http://jira.codehaus.org/browse/SUREFIRE-672
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
> Affects Versions: 2.7
> Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
> IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr7-20100219_54049 (JIT enabled, AOT enabled)
> OS name: "windows xp" version: "5.1 build 2600 service pack 3" arch: "x86" Family: "windows"
> Reporter: Jan Fredrik Wedén
> Assignee: Kristian Rosenvold
> Priority: Blocker
> Fix For: 2.7.1
>
>
> Upgrading maven-failsafe-plugin from version 2.6 to 2.7 causes builds with integration test errors to be reported as successful.
> From my understanding, the failsafe verify goal uses the summary file (default: target\failsafe-reports\failsafe-summary.xml) to check whether executed integration tests passed or had any errors. I've pasted the content of this file below as it is generated by the failsafe plugin version 2.6 and 2.7 respectively for the same build with the same integration test errors. It appears that the integration-test goal does not generate this file correctly in version 2.7.
> {code:title=failsafe plugin v2.6: failsafe-summary.xml|language=XML}
> <?xml version="1.0" encoding="UTF-8"?>
> <failsafe-summary result="255" />
> {code}
> {code:title=failsafe plugin v2.7: failsafe-summary.xml|language=XML}
> <?xml version="1.0" encoding="UTF-8"?>
> <failsafe-summary />
> {code}
> The result for this build is that the failsafe plugin version 2.6 fails the build (as it should) while failsafe plugin version 2.7 does not and the build is reported as successful.
--
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-672) Failsafe no longer fails builds
due to broken failsafe-summary.xml file
Posted by "Jan Fredrik Wedén (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249388#action_249388 ]
Jan Fredrik Wedén commented on SUREFIRE-672:
--------------------------------------------
Tested the same build containing failing tests with maven-failsafe-plugin-2.7.1-20101222.020133-14. The summary file now once again contains the same stuff as 2.6 produced and the build is failed. Great, thanks! :)
> Failsafe no longer fails builds due to broken failsafe-summary.xml file
> -----------------------------------------------------------------------
>
> Key: SUREFIRE-672
> URL: http://jira.codehaus.org/browse/SUREFIRE-672
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
> Affects Versions: 2.7
> Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
> IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr7-20100219_54049 (JIT enabled, AOT enabled)
> OS name: "windows xp" version: "5.1 build 2600 service pack 3" arch: "x86" Family: "windows"
> Reporter: Jan Fredrik Wedén
> Assignee: Kristian Rosenvold
> Priority: Blocker
> Fix For: 2.7.1
>
>
> Upgrading maven-failsafe-plugin from version 2.6 to 2.7 causes builds with integration test errors to be reported as successful.
> From my understanding, the failsafe verify goal uses the summary file (default: target\failsafe-reports\failsafe-summary.xml) to check whether executed integration tests passed or had any errors. I've pasted the content of this file below as it is generated by the failsafe plugin version 2.6 and 2.7 respectively for the same build with the same integration test errors. It appears that the integration-test goal does not generate this file correctly in version 2.7.
> {code:title=failsafe plugin v2.6: failsafe-summary.xml|language=XML}
> <?xml version="1.0" encoding="UTF-8"?>
> <failsafe-summary result="255" />
> {code}
> {code:title=failsafe plugin v2.7: failsafe-summary.xml|language=XML}
> <?xml version="1.0" encoding="UTF-8"?>
> <failsafe-summary />
> {code}
> The result for this build is that the failsafe plugin version 2.6 fails the build (as it should) while failsafe plugin version 2.7 does not and the build is reported as successful.
--
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-672) Failsafe no longer fails builds due
to broken failsafe-summary.xml file
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold closed SUREFIRE-672.
---------------------------------------
Resolution: Fixed
Funny how a failing build once again makes us happy. Shame this one got through, thanks for testing !
> Failsafe no longer fails builds due to broken failsafe-summary.xml file
> -----------------------------------------------------------------------
>
> Key: SUREFIRE-672
> URL: http://jira.codehaus.org/browse/SUREFIRE-672
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
> Affects Versions: 2.7
> Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
> IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr7-20100219_54049 (JIT enabled, AOT enabled)
> OS name: "windows xp" version: "5.1 build 2600 service pack 3" arch: "x86" Family: "windows"
> Reporter: Jan Fredrik Wedén
> Assignee: Kristian Rosenvold
> Priority: Blocker
> Fix For: 2.7.1
>
>
> Upgrading maven-failsafe-plugin from version 2.6 to 2.7 causes builds with integration test errors to be reported as successful.
> From my understanding, the failsafe verify goal uses the summary file (default: target\failsafe-reports\failsafe-summary.xml) to check whether executed integration tests passed or had any errors. I've pasted the content of this file below as it is generated by the failsafe plugin version 2.6 and 2.7 respectively for the same build with the same integration test errors. It appears that the integration-test goal does not generate this file correctly in version 2.7.
> {code:title=failsafe plugin v2.6: failsafe-summary.xml|language=XML}
> <?xml version="1.0" encoding="UTF-8"?>
> <failsafe-summary result="255" />
> {code}
> {code:title=failsafe plugin v2.7: failsafe-summary.xml|language=XML}
> <?xml version="1.0" encoding="UTF-8"?>
> <failsafe-summary />
> {code}
> The result for this build is that the failsafe plugin version 2.6 fails the build (as it should) while failsafe plugin version 2.7 does not and the build is reported as successful.
--
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