[Gluster-devel] regression burn-in summary over the last 7 days
Vijay Bellur
vbellur at redhat.com
Fri Aug 5 03:02:07 UTC 2016
On Wed, Aug 3, 2016 at 1:37 PM, Atin Mukherjee <amukherj at redhat.com> wrote:
> I think we should compare n-1th week report with nth and any common tests
> out of that comparison having more than or equal to 3 instances of failures
> SHOULD immediately marked as bad and any component having more than 5 bad
> tests should be BLOCKED for further merges till bad tests are fixed. What do
> others think about it?
>
If we can automate this workflow, I am in favor of the proposal.
-Vijay
More information about the Gluster-devel
mailing list