Re: good job on fixing heavy hitters in spurious regressions

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

 




On 05/08/2015 05:27 PM, Jeff Darcy wrote:
I think we should remove "if it is a known bad test treat it as success"
code in some time and never add it again in future.
I disagree.  We were in a cycle where a fix for one bad regression test
would be blocked because of others, so it was impossible to make any
progress at all.  The cycle had to be broken somehow.  What we should
really do next time is get more people involved sooner when regression
tests are broken.  That way we'd never get into the "death spiral" and
no drastic action would be necessary.
Thanks for that effort!, I was talking about the plan for future, not what has been done. Anyways people seem to like the idea that they can look at the tests in that file to know if the test is bad or not, so may be it will live on.

Pranith

_______________________________________________
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