Re: NetBSD tests not running to completion.

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

 



Avra Sengupta <asengupt@xxxxxxxxxx> wrote:

> Agree with your point. If we are ready to make exceptions, then we might
> as well not block all the patches. As Jeff suggested, triaging the 
> nightly/weekly results manually and making any serious issues a blocker
> should suffice. 

How are you going to make a serious issue a blocker? The serious issue
will be related to multiple patches, it will be impossible to tell which
one is the offender.

If we go that way, we need to run a regression for each merged patch,
which will be much less load than today.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@xxxxxxxxxx
_______________________________________________
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