On Mon, Jul 20, 2015 at 09:25:15AM +0530, Ravishankar N wrote: > I'll take a look. Thanks. I'm actually not sure if this is a arbiter.t issue, maybe I blamed it too early? Its the first test that gets executed, and no others are tried after it failed. Niels > Regards, > Ravi > > On 07/20/2015 03:07 AM, Niels de Vos wrote: > >I have seen several occurences of failures in arbiter.t now. This is one > >of the errors: > > > > https://build.gluster.org/job/rackspace-regression-2GB-triggered/12626/consoleFull > > > > [21:20:20] ./tests/basic/afr/arbiter.t .. > > not ok 7 Got "N" instead of "Y" > > not ok 15 > > not ok 16 Got "" instead of "1" > > not ok 23 Got "" instead of "1" > > not ok 25 Got "0" when not expecting it > > not ok 26 > > not ok 34 Got "0" instead of "1" > > not ok 35 Got "0" instead of "1" > > not ok 41 Got "" instead of "1" > > not ok 47 Got "N" instead of "Y" > > Failed 10/47 subtests > > [21:20:20] > > Test Summary Report > > ------------------- > > ./tests/basic/afr/arbiter.t (Wstat: 0 Tests: 47 Failed: 10) > > Failed tests: 7, 15-16, 23, 25-26, 34-35, 41, 47 > > Files=1, Tests=47, 243 wallclock secs ( 0.04 usr 0.00 sys + 15.22 cusr 3.48 csys = 18.74 CPU) > > Result: FAIL > > > > > >Who could have look at this? > > > >Thanks, > >Niels > >_______________________________________________ > >Gluster-devel mailing list > >Gluster-devel@xxxxxxxxxxx > >http://www.gluster.org/mailman/listinfo/gluster-devel > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
