On Mon, Nov 14, 2016 at 10:34 PM, Nithya Balachandran <nbalacha@xxxxxxxxxx> wrote: > > > On 14 November 2016 at 21:38, Vijay Bellur <vbellur@xxxxxxxxxx> wrote: >> >> I would prefer that we disable dbench only if we have an owner for >> fixing the problem and re-enabling it as part of smoke tests. Running >> dbench seamlessly on gluster has worked for a long while and if it is >> failing today, we need to address this regression asap. >> >> Does anybody have more context or clues on why dbench is failing now? >> > While I agree that it needs to be looked at asap, leaving it in until we get > an owner seems rather pointless as all it does is hold up various patches > and waste machine time. Re-triggering it multiple times so that it > eventually passes does not add anything to the regression test processes or > validate the patch as we know there is a problem. > > I would vote for removing it and assigning someone to look at it > immediately. > >From the debugging done so far can we identify an owner to whom this can be assigned? I looked around for related discussions and could figure out that we are looking to get statedumps. Do we have more information/context beyond this? Regards, Vijay _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
