[Gluster-devel] Upstream smoke test failures

Atin Mukherjee amukherj at redhat.com
Tue Nov 15 03:46:42 UTC 2016


On Tue, Nov 15, 2016 at 9:04 AM, Nithya Balachandran <nbalacha at redhat.com>
wrote:

>
>
> On 14 November 2016 at 21:38, Vijay Bellur <vbellur at redhat.com> 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 echo the same.


>
> I would vote for removing it and assigning someone to look at it
> immediately.
>
> Regards,
> Nithya
>
> Thanks!
>> Vijay
>>
>> On Mon, Nov 14, 2016 at 3:45 AM, Nigel Babu <nigelb at redhat.com> 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 at redhat.com> 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 at gluster.org
>> > http://www.gluster.org/mailman/listinfo/gluster-devel
>> _______________________________________________
>> Gluster-devel mailing list
>> Gluster-devel at gluster.org
>> http://www.gluster.org/mailman/listinfo/gluster-devel
>>
>
>
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
>



-- 

~ Atin (atinm)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-devel/attachments/20161115/9d376b6d/attachment.html>


More information about the Gluster-devel mailing list