Re: good job on fixing heavy hitters in spurious regressions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 8 May 2015, at 04:15, Pranith Kumar Karampuri <pkarampu@xxxxxxxxxx> wrote:
<snip>
> 2) If the same test fails on different patches more than 'x' number of times we should do something drastic. Let us decide on 'x' and what the drastic measure is.

Sure.  That number is 0.

If it fails more than 0 times on different patches, we have
a problem than needs resolving as an immediate priority.


<snip>
> Some good things I found this time around compared to 3.6.0 release:
> 1) Failing the regression on first failure is helping locating the failure logs really fast
> 2) More people chipped in fixing the tests that are not at all their responsibility, which is always great to see.

Cool. :)

+ Justin

--
GlusterFS - http://www.gluster.org

An open source, distributed file system scaling to several
petabytes, and handling thousands of clients.

My personal twitter: twitter.com/realjustinclift

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel




[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux