On Wed, Aug 3, 2016 at 1:37 PM, Atin Mukherjee <[email protected]> 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
_______________________________________________
Gluster-devel mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-devel

Reply via email to