[jira] [Commented] (HBASE-11381) Isolate and rerun unit tests that fail following a code commit

["Dima Spivak (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038095#comment-14038095 ] 

Dima Spivak commented on HBASE-11381:
-------------------------------------

To provide a few more concrete details on the logistics of this, the Jenkins [Naginator Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Naginator+Plugin] seems well-suited for this task. Note that the newly triggered builds could specifically be set to use the previous build's artifacts so that the exact same bits are retested.

> Isolate and rerun unit tests that fail following a code commit
> --------------------------------------------------------------
>
>                 Key: HBASE-11381
>                 URL: https://issues.apache.org/jira/browse/HBASE-11381
>             Project: HBase
>          Issue Type: Task
>            Reporter: Dima Spivak
>
> It's not uncommon to see that, after changes are committed to a branch, a set of unit tests will begin to fail and Hudson will add a comment to the relevant JIRAs reporting on the unsuccessful build. Unfortunately, these test failures are not always indicative of regressions; sometimes, the problem is with infrastructure and simply rerunning the tests can make them go green again.
> I propose modifying the Jenkins job that is triggered by a code commit to address this problem. In particular, the job could use the reports generated by the Maven Surefire plugin to generate a list of tests to rerun. These tests can be set to rerun any number of times and a threshold ratio of passes-to-fails can be the deciding factor in whether a real bug has been introduced following a change in HBase.



--
This message was sent by Atlassian JIRA
(v6.2#6252)