On 05/07/2015 09:26 AM, Atin Mukherjee wrote: > > > On 05/07/2015 01:24 AM, Jeff Darcy wrote: >>>> * tests/basic/volume-snapshot-clone.t >>>> >>>> * http://review.gluster.org/#/c/10053/ >>>> >>>> * Came back on April 9 >>>> >>>> * http://build.gluster.org/job/rackspace-regression-2GB-triggered/6658/ >>>> >>> >>> Rafi - does this happen anymore? If fixed due to subsequent commits, we >>> should look at dropping this test from is_bad_test() in run-tests.sh. >> >> I'm still seeing this one quite a lot in logs, though the errors are >> being ignored. > Yesterday I started looking into it. I will update once I progress on > the analysis. http://review.gluster.org/#/c/10619/ should address it. ~Atin > > ~Atin >> >>>> * tests/basic/uss.t >>>> >>>> * https://bugzilla.redhat.com/show_bug.cgi?id=1209286 >>>> >>>> * http://review.gluster.org/#/c/10143/ >>>> >>>> * Came back on April 9 >>>> >>>> * http://build.gluster.org/job/rackspace-regression-2GB-triggered/6660/ >>>> >>>> * ./tests/bugs/glusterfs/bug-867253.t (Wstat: 0 Tests: 9 Failed: 1) >>>> >>>> * Failed test: 8 >>>> >>> >>> Raghu - does this happen anymore? If fixed due to subsequent commits, we >>> should look at dropping this test from is_bad_test() in run-tests.sh. >> >> Same for this one. If we re-enabled result checking for these two, maybe >> half of our test runs would start failing again. >> >> _______________________________________________ >> Gluster-devel mailing list >> Gluster-devel@xxxxxxxxxxx >> http://www.gluster.org/mailman/listinfo/gluster-devel >> > -- ~Atin _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
