IIRC, we were marking the verified as +1 in case of a known spurious failure, can't we continue to do the same for the known spurious failures just to unblock the patches getting merged till the problems are resolved? ~Atin On 08/22/2014 11:44 PM, Vijay Bellur wrote: > On 06/12/2014 09:06 PM, Pranith Kumar Karampuri wrote: >> Avra/Poornima, >> Please look into this. >> >> Patch ==> http://review.gluster.com/#/c/6483/9 >> Author ==> Poornima pgurusid@xxxxxxxxxx >> Build triggered by ==> amarts >> Build-url ==> >> http://build.gluster.org/job/regression/4847/consoleFull >> Download-log-at ==> >> http://build.gluster.org:443/logs/regression/glusterfs-logs-20140612:08:37:44.tgz >> >> >> Test written by ==> Author: Avra Sengupta <asengupt@xxxxxxxxxx> > > > > Any update on this? Found yet another failure [1] of this particular > testcase. > > -Vijay > > [1] > http://build.gluster.org/job/rackspace-regression-2GB-triggered/979/consoleFull > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > http://supercolony.gluster.org/mailman/listinfo/gluster-devel _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-devel
