[
https://issues.apache.org/jira/browse/HBASE-10570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906370#comment-13906370
]
Hudson commented on HBASE-10570:
--------------------------------
SUCCESS: Integrated in HBase-TRUNK #4934 (See
[https://builds.apache.org/job/HBase-TRUNK/4934/])
HBASE-10570 Allow overrides of Surefire secondPartForkMode and
testFailureIgnore (apurtell: rev 1569935)
* /hbase/trunk/pom.xml
> 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)
