You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ondrej Zizka (JIRA)" <ji...@codehaus.org> on 2011/12/02 05:08:40 UTC
[jira] Created: (SUREFIRE-803) Multiple Surefire executions -
FAILURE in an execution prevents successive from running.
Multiple Surefire executions - FAILURE in an execution prevents successive from running.
----------------------------------------------------------------------------------------
Key: SUREFIRE-803
URL: https://jira.codehaus.org/browse/SUREFIRE-803
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 2.10
Reporter: Ondrej Zizka
Priority: Critical
Let's have multiple Surefire executions in a single module (different config needed).
A failure of a test in one of these executions prevents running the successive.
Surefire's testFailureIgnore is not an option because it makes a run with failures succeed.
This behavior is undocumented.
Also, it is undesired - the module as a whole should fail, but all it's tests should run.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-803) Multiple Surefire executions - FAILURE in an
execution prevents successive from running.
Posted by "Stephen Connolly (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285598#comment-285598 ]
Stephen Connolly commented on SUREFIRE-803:
-------------------------------------------
We write the results to an XML file so that other tools, such as CI tools (e.g. Jenkins), can parse the results. Or are you asking a different question
> Multiple Surefire executions - FAILURE in an execution prevents successive from running.
> ----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-803
> URL: https://jira.codehaus.org/browse/SUREFIRE-803
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.10
> Reporter: Ondrej Zizka
> Assignee: John Casey
> Priority: Critical
> Attachments: surefire-803-failure-prevents-subsequent-executions.zip
>
>
> Let's have multiple Surefire executions in a single module (different config needed).
> A failure of a test in one of these executions prevents running the successive.
> Surefire's testFailureIgnore is not an option because it makes a run with failures succeed.
> This behavior is undocumented.
> Also, it is undesired - the module as a whole should fail, but all it's tests should run.
--
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
[jira] Commented: (SUREFIRE-803) Multiple Surefire executions -
FAILURE in an execution prevents successive from running.
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284950#comment-284950 ]
Kristian Rosenvold commented on SUREFIRE-803:
---------------------------------------------
Can't you just use the maven -fae option ?
> Multiple Surefire executions - FAILURE in an execution prevents successive from running.
> ----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-803
> URL: https://jira.codehaus.org/browse/SUREFIRE-803
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.10
> Reporter: Ondrej Zizka
> Priority: Critical
>
> Let's have multiple Surefire executions in a single module (different config needed).
> A failure of a test in one of these executions prevents running the successive.
> Surefire's testFailureIgnore is not an option because it makes a run with failures succeed.
> This behavior is undocumented.
> Also, it is undesired - the module as a whole should fail, but all it's tests should run.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-803) Multiple Surefire executions -
FAILURE in an execution prevents successive from running.
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285241#comment-285241 ]
John Casey commented on SUREFIRE-803:
-------------------------------------
Something akin to what the failsafe plugin does might work, but it'd require a surefire mojo executing later in the build process to read the reports and trigger the build failure...which means running `mvn clean test
> Multiple Surefire executions - FAILURE in an execution prevents successive from running.
> ----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-803
> URL: https://jira.codehaus.org/browse/SUREFIRE-803
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.10
> Reporter: Ondrej Zizka
> Priority: Critical
>
> Let's have multiple Surefire executions in a single module (different config needed).
> A failure of a test in one of these executions prevents running the successive.
> Surefire's testFailureIgnore is not an option because it makes a run with failures succeed.
> This behavior is undocumented.
> Also, it is undesired - the module as a whole should fail, but all it's tests should run.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-803) Multiple Surefire executions - FAILURE in an
execution prevents successive from running.
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285659#comment-285659 ]
John Casey commented on SUREFIRE-803:
-------------------------------------
Do we have other cases where we're using the pluginContext for this sort of state? I know that's the point of the context, but it used to be broken once upon a time, and I'd be interested in seeing some prior art. Otherwise, I suppose we could try that and fall back to a file if it doesn't work.
I'm fine with changing the default behavior, since I think it's unlikely most people will really be able to tell. But does that mean the 'test' phase will actually run both surefire:test and surefire:verify, or would surefire:test actually run somewhere earlier (where, that it won't interfere with setting up the test classes?)...or, would users need to know that running `mvn clean test` no longer verifies the outcome of the surefire tests?
Or...are we hoping to pin verification to the end of the list of executions, using the pluginContext to detect that end? In effect, making it still be "built into" the surefire:test goal rather than splitting it into a surefire:verify goal?
> Multiple Surefire executions - FAILURE in an execution prevents successive from running.
> ----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-803
> URL: https://jira.codehaus.org/browse/SUREFIRE-803
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
> Affects Versions: 2.10
> Reporter: Ondrej Zizka
> Assignee: John Casey
> Attachments: surefire-803-failure-prevents-subsequent-executions.zip
>
>
> Let's have multiple Surefire executions in a single module (different config needed).
> A failure of a test in one of these executions prevents running the successive.
> Surefire's testFailureIgnore is not an option because it makes a run with failures succeed.
> This behavior is undocumented.
> Also, it is undesired - the module as a whole should fail, but all it's tests should run.
--
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
[jira] (SUREFIRE-803) Multiple Surefire executions - FAILURE in an
execution prevents successive from running.
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285672#comment-285672 ]
Kristian Rosenvold commented on SUREFIRE-803:
---------------------------------------------
I think Stephen makes a 3/4 decent argument for keeping it in the xml file.
The way I see this, the change will /not/ be modifying the surefire plugin, but only failsafe. So the user would typically replace surefire with failsafe, and then run "mvn verify" instead of "mvn test". Any executions of the failsafe plugin would simply record/update the file, and any executions from test to integration-test would simply amend their results, we're only interested in toggling from success->failure anyway, so that should be ok. This would of course leave us with the problem of /when to delete/ the file, and I suppose we could use the pluginContext for that, because Stephen seems to indicate there may be tools using that file.
With the exception of amending to the current result, this is much the way failsafe works today, so it should be a tiny patch. Making some nice IT's is probably going to be half the effort...
I am trying hard to remember the last time I used the pluginContext. It works, I have done it. I just can't remember when; argh. This /will/ wake me up tonight....
> Multiple Surefire executions - FAILURE in an execution prevents successive from running.
> ----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-803
> URL: https://jira.codehaus.org/browse/SUREFIRE-803
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
> Affects Versions: 2.10
> Reporter: Ondrej Zizka
> Assignee: John Casey
> Attachments: surefire-803-failure-prevents-subsequent-executions.zip
>
>
> Let's have multiple Surefire executions in a single module (different config needed).
> A failure of a test in one of these executions prevents running the successive.
> Surefire's testFailureIgnore is not an option because it makes a run with failures succeed.
> This behavior is undocumented.
> Also, it is undesired - the module as a whole should fail, but all it's tests should run.
--
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
[jira] Commented: (SUREFIRE-803) Multiple Surefire executions -
FAILURE in an execution prevents successive from running.
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285336#comment-285336 ]
Kristian Rosenvold commented on SUREFIRE-803:
---------------------------------------------
The current failsafe verification could be modified to consider results for multiple executions. In 2.11 we actually already write a file that tells us how the build progressed (with runOrder=failedfirst or runOrder=balanced), and this would write a separate file for each execution. I suppose someone could write a patch that scans these files and make the verify phase in failsafe use these to evaluate if the build failed.
There might be a few hoops to jump through regarding which files to read, but that should be solveable.
> Multiple Surefire executions - FAILURE in an execution prevents successive from running.
> ----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-803
> URL: https://jira.codehaus.org/browse/SUREFIRE-803
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.10
> Reporter: Ondrej Zizka
> Priority: Critical
> Attachments: surefire-803-failure-prevents-subsequent-executions.zip
>
>
> Let's have multiple Surefire executions in a single module (different config needed).
> A failure of a test in one of these executions prevents running the successive.
> Surefire's testFailureIgnore is not an option because it makes a run with failures succeed.
> This behavior is undocumented.
> Also, it is undesired - the module as a whole should fail, but all it's tests should run.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-803) Multiple Surefire executions -
FAILURE in an execution prevents successive from running.
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285348#comment-285348 ]
John Casey commented on SUREFIRE-803:
-------------------------------------
My big question would be where in the build lifecycle the tests execute, vs. where they get verified.
Also, would this be a mode of operation that we turn on, or would users with the simpler use case experience a different build plan as a result of this change?
> Multiple Surefire executions - FAILURE in an execution prevents successive from running.
> ----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-803
> URL: https://jira.codehaus.org/browse/SUREFIRE-803
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.10
> Reporter: Ondrej Zizka
> Priority: Critical
> Attachments: surefire-803-failure-prevents-subsequent-executions.zip
>
>
> Let's have multiple Surefire executions in a single module (different config needed).
> A failure of a test in one of these executions prevents running the successive.
> Surefire's testFailureIgnore is not an option because it makes a run with failures succeed.
> This behavior is undocumented.
> Also, it is undesired - the module as a whole should fail, but all it's tests should run.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-803) Multiple Surefire executions - FAILURE in an
execution prevents successive from running.
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285535#comment-285535 ]
Kristian Rosenvold commented on SUREFIRE-803:
---------------------------------------------
I think this could probably go "as is" wrt the current failsafe plugin. I somehow think we can just change the default behaviour on this one; if a user currently has multiple executions of failsafe she'll be losing the results from one of the invocations; i just don't see the use case where the existing behaviour makes sense (unless you also attach ver ify multiple places, but that wouldn't change even if we did this change).
Regarding how to detect which executions have been done, I've been wondering if we could just keep a list of executions in the pluginContext ? I'm not sure why we need to write the results to a file (and an xml file, just to be sure..). Maybe stephen has some input on this..
> Multiple Surefire executions - FAILURE in an execution prevents successive from running.
> ----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-803
> URL: https://jira.codehaus.org/browse/SUREFIRE-803
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.10
> Reporter: Ondrej Zizka
> Assignee: John Casey
> Priority: Critical
> Attachments: surefire-803-failure-prevents-subsequent-executions.zip
>
>
> Let's have multiple Surefire executions in a single module (different config needed).
> A failure of a test in one of these executions prevents running the successive.
> Surefire's testFailureIgnore is not an option because it makes a run with failures succeed.
> This behavior is undocumented.
> Also, it is undesired - the module as a whole should fail, but all it's tests should run.
--
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
[jira] Commented: (SUREFIRE-803) Multiple Surefire executions -
FAILURE in an execution prevents successive from running.
Posted by "Ondrej Zizka (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285307#comment-285307 ]
Ondrej Zizka commented on SUREFIRE-803:
---------------------------------------
Running a set of tests is a natural concept of the build process.
I'd say that Maven core should be aware of this concept and should be given the information about how the tests ran.
I don't know how it's implemented but I'd imagine some broader interface for Surefire, with methods to get the results info.
> Multiple Surefire executions - FAILURE in an execution prevents successive from running.
> ----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-803
> URL: https://jira.codehaus.org/browse/SUREFIRE-803
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.10
> Reporter: Ondrej Zizka
> Priority: Critical
> Attachments: surefire-803-failure-prevents-subsequent-executions.zip
>
>
> Let's have multiple Surefire executions in a single module (different config needed).
> A failure of a test in one of these executions prevents running the successive.
> Surefire's testFailureIgnore is not an option because it makes a run with failures succeed.
> This behavior is undocumented.
> Also, it is undesired - the module as a whole should fail, but all it's tests should run.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-803) Multiple Surefire executions -
FAILURE in an execution prevents successive from running.
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated SUREFIRE-803:
--------------------------------
Attachment: surefire-803-failure-prevents-subsequent-executions.zip
I believe this is the basic test case that distills the issue. Of course, multimodule builds may also exhibit the symptom found here, but they also obscure the essential bug, IMO. Fix this test case, and the multimodule case will be fixed as well.
> Multiple Surefire executions - FAILURE in an execution prevents successive from running.
> ----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-803
> URL: https://jira.codehaus.org/browse/SUREFIRE-803
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.10
> Reporter: Ondrej Zizka
> Priority: Critical
> Attachments: surefire-803-failure-prevents-subsequent-executions.zip
>
>
> Let's have multiple Surefire executions in a single module (different config needed).
> A failure of a test in one of these executions prevents running the successive.
> Surefire's testFailureIgnore is not an option because it makes a run with failures succeed.
> This behavior is undocumented.
> Also, it is undesired - the module as a whole should fail, but all it's tests should run.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-803) Multiple Surefire executions - FAILURE in an
execution prevents successive from running.
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed SUREFIRE-803.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.12
Added code to store/check a token in the plugin context to determine whether the failsafe summary already on disk is from a previous execution in the current build vs. output from a previous build.
Then, modified to accumulate test results in the failsafe summary instead of overwriting (overwrite still happens if the existing output is not from the current build). This allows multiple failsafe executions in a build without coping with different output locations for the summaries.
See revIds 1232091 and 1233522.
> Multiple Surefire executions - FAILURE in an execution prevents successive from running.
> ----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-803
> URL: https://jira.codehaus.org/browse/SUREFIRE-803
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
> Affects Versions: 2.10
> Reporter: Ondrej Zizka
> Assignee: John Casey
> Fix For: 2.12
>
> Attachments: surefire-803-failure-prevents-subsequent-executions.zip
>
>
> Let's have multiple Surefire executions in a single module (different config needed).
> A failure of a test in one of these executions prevents running the successive.
> Surefire's testFailureIgnore is not an option because it makes a run with failures succeed.
> This behavior is undocumented.
> Also, it is undesired - the module as a whole should fail, but all it's tests should run.
--
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
[jira] Commented: (SUREFIRE-803) Multiple Surefire executions -
FAILURE in an execution prevents successive from running.
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285238#comment-285238 ]
Paul Gier commented on SUREFIRE-803:
------------------------------------
I'm not sure how this could be fixed in Surefire without changes to Maven core. There would need to be a change to Maven, maybe a new Mojo Exception that would tell Maven that there was a failure but that it's ok to continue building the module.
> Multiple Surefire executions - FAILURE in an execution prevents successive from running.
> ----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-803
> URL: https://jira.codehaus.org/browse/SUREFIRE-803
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.10
> Reporter: Ondrej Zizka
> Priority: Critical
>
> Let's have multiple Surefire executions in a single module (different config needed).
> A failure of a test in one of these executions prevents running the successive.
> Surefire's testFailureIgnore is not an option because it makes a run with failures succeed.
> This behavior is undocumented.
> Also, it is undesired - the module as a whole should fail, but all it's tests should run.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-803) Multiple Surefire executions -
FAILURE in an execution prevents successive from running.
Posted by "Ondrej Zizka (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285129#comment-285129 ]
Ondrej Zizka commented on SUREFIRE-803:
---------------------------------------
No, that helps with executions in multiple modules, where each has one.
I am talking about **multiple executions** in **single module**.
> Multiple Surefire executions - FAILURE in an execution prevents successive from running.
> ----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-803
> URL: https://jira.codehaus.org/browse/SUREFIRE-803
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.10
> Reporter: Ondrej Zizka
> Priority: Critical
>
> Let's have multiple Surefire executions in a single module (different config needed).
> A failure of a test in one of these executions prevents running the successive.
> Surefire's testFailureIgnore is not an option because it makes a run with failures succeed.
> This behavior is undocumented.
> Also, it is undesired - the module as a whole should fail, but all it's tests should run.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (SUREFIRE-803) Multiple Surefire
executions - FAILURE in an execution prevents successive from running.
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285241#comment-285241 ]
John Casey edited comment on SUREFIRE-803 at 12/8/11 11:39 AM:
---------------------------------------------------------------
Something akin to what the failsafe plugin does might work, but it'd require a surefire mojo executing later in the build process to read the reports and trigger the build failure...which means running `mvn clean test` might not cut it without re-shuffling the surefire executions to some earlier phase.
There might be other ways to detect whether the current execution is the last (and therefore whether it's okay to fail the build now), but I'm not sure off the top of my head.
was (Author: jdcasey):
Something akin to what the failsafe plugin does might work, but it'd require a surefire mojo executing later in the build process to read the reports and trigger the build failure...which means running `mvn clean test
> Multiple Surefire executions - FAILURE in an execution prevents successive from running.
> ----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-803
> URL: https://jira.codehaus.org/browse/SUREFIRE-803
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.10
> Reporter: Ondrej Zizka
> Priority: Critical
>
> Let's have multiple Surefire executions in a single module (different config needed).
> A failure of a test in one of these executions prevents running the successive.
> Surefire's testFailureIgnore is not an option because it makes a run with failures succeed.
> This behavior is undocumented.
> Also, it is undesired - the module as a whole should fail, but all it's tests should run.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-803) Multiple Failsafe executions - FAILURE in an
execution prevents successive from running.
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated SUREFIRE-803:
--------------------------------
Component/s: (was: Maven Surefire Plugin)
Maven Failsafe Plugin
Summary: Multiple Failsafe executions - FAILURE in an execution prevents successive from running. (was: Multiple Surefire executions - FAILURE in an execution prevents successive from running.)
NOTE: NOT fixing this for the surefire plugin, only modifying the failsafe plugin a little bit. This is because the failsafe plugin is better equipped to handle the non-fail-fast use case.
> Multiple Failsafe executions - FAILURE in an execution prevents successive from running.
> ----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-803
> URL: https://jira.codehaus.org/browse/SUREFIRE-803
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Failsafe Plugin
> Affects Versions: 2.10
> Reporter: Ondrej Zizka
> Assignee: John Casey
> Fix For: 2.12
>
> Attachments: surefire-803-failure-prevents-subsequent-executions.zip
>
>
> Let's have multiple Surefire executions in a single module (different config needed).
> A failure of a test in one of these executions prevents running the successive.
> Surefire's testFailureIgnore is not an option because it makes a run with failures succeed.
> This behavior is undocumented.
> Also, it is undesired - the module as a whole should fail, but all it's tests should run.
--
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
[jira] (SUREFIRE-803) Multiple Surefire executions - FAILURE in an
execution prevents successive from running.
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold updated SUREFIRE-803:
----------------------------------------
Priority: Major (was: Critical)
Issue Type: Improvement (was: Bug)
> Multiple Surefire executions - FAILURE in an execution prevents successive from running.
> ----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-803
> URL: https://jira.codehaus.org/browse/SUREFIRE-803
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
> Affects Versions: 2.10
> Reporter: Ondrej Zizka
> Assignee: John Casey
> Attachments: surefire-803-failure-prevents-subsequent-executions.zip
>
>
> Let's have multiple Surefire executions in a single module (different config needed).
> A failure of a test in one of these executions prevents running the successive.
> Surefire's testFailureIgnore is not an option because it makes a run with failures succeed.
> This behavior is undocumented.
> Also, it is undesired - the module as a whole should fail, but all it's tests should run.
--
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