[
https://issues.apache.org/jira/browse/HBASE-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kyle Purtell resolved HBASE-11381.
-----------------------------------------
Resolution: Later
> 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
> Priority: Major
>
> 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
(v8.20.7#820007)
