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? Thanks! Vijay On Mon, Nov 14, 2016 at 3:45 AM, Nigel Babu <nigelb@xxxxxxxxxx> wrote: > It looks like. Nithya asked me to get some numbers. > > The first failure was on Aug 2nd [1]. Here are the monthly numbers since > August: > > Aug: 31 > Sep: 59 > Oct: 107 > Nov: 43 (in 14 days) > > [1]: https://build.gluster.org/job/smoke/29605/consoleText > > On Sun, Nov 13, 2016 at 10:04:58PM -0800, Joe Julian wrote: >> Does this mean race conditions are in master and are just being retried until they're not hit? >> >> On November 13, 2016 9:33:51 PM PST, Nithya Balachandran <nbalacha@xxxxxxxxxx> wrote: >> >Hi, >> > >> >Our smoke tests have been failing quite frequently of late. While >> >re-triggering smoke several times in order to get a +1 works >> >eventually, >> >this does not really help anything IMO. >> > >> >I believe Jeff has already proposed this earlier but can we remove the >> >failing dbench tests from smoke until we figure out what is going on? > > -- > nigelb > _______________________________________________ > 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
