You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2014/02/19 19:32:20 UTC

[jira] [Updated] (HBASE-10570) Allow overrides of Surefire secondPartForkMode and testFailureIgnore

     [ https://issues.apache.org/jira/browse/HBASE-10570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Purtell updated HBASE-10570:
-----------------------------------

    Attachment: 10570.patch

> Allow overrides of Surefire secondPartForkMode and testFailureIgnore
> --------------------------------------------------------------------
>
>                 Key: HBASE-10570
>                 URL: https://issues.apache.org/jira/browse/HBASE-10570
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>            Priority: Minor
>             Fix For: 0.96.2, 0.98.1, 0.99.0
>
>         Attachments: 10570.patch
>
>
> It can be useful to override the fork and ignore behavior of our Surefire unit testing machinery. 
> For example, this will put only one test into each generated surefire jar and always fork a child JVM to run it:
> {noformat}
> mvn test ... -Dsurefire.firstPartForkMode=always -Dsurefire.secondPartForkMode=always
> {noformat}
> Useful for isolating test failures and finding zombies.
> Sometimes it is also useful to ignore test failures:
> {noformat}
> mvn test ... -Dsurefire.testFailureIgnore=true
> {noformat}
> This will let test suite execution continue even if a test times out. Maven has CLI options for this sort of thing but they don't always work as expected. 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)