<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 15, 2016 at 9:04 AM, Nithya Balachandran <span dir="ltr"><<a href="mailto:nbalacha@redhat.com" target="_blank">nbalacha@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On 14 November 2016 at 21:38, Vijay Bellur <span dir="ltr"><<a href="mailto:vbellur@redhat.com" target="_blank">vbellur@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I would prefer that we disable dbench only if we have an owner for<br>
fixing the problem and re-enabling it as part of smoke tests. Running<br>
dbench seamlessly on gluster has worked for a long while and if it is<br>
failing today, we need to address this regression asap.<br>
<br>
Does anybody have more context or clues on why dbench is failing now?<br>
<br></blockquote></span><div>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.</div></div></div></div></blockquote><div><br></div><div>I echo the same.<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>I would vote for removing it and assigning someone to look at it immediately.</div><div><br></div><div>Regards,</div><div>Nithya</div><div><div class="h5"><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks!<br>
<span class="m_4785646050033083736HOEnZb"><font color="#888888">Vijay<br>
</font></span><div><div class="m_4785646050033083736h5"><br>
On Mon, Nov 14, 2016 at 3:45 AM, Nigel Babu <<a href="mailto:nigelb@redhat.com" target="_blank">nigelb@redhat.com</a>> wrote:<br>
> It looks like. Nithya asked me to get some numbers.<br>
><br>
> The first failure was on Aug 2nd [1]. Here are the monthly numbers since<br>
> August:<br>
><br>
> Aug: 31<br>
> Sep: 59<br>
> Oct: 107<br>
> Nov: 43 (in 14 days)<br>
><br>
> [1]: <a href="https://build.gluster.org/job/smoke/29605/consoleText" rel="noreferrer" target="_blank">https://build.gluster.org/job/<wbr>smoke/29605/consoleText</a><br>
><br>
> On Sun, Nov 13, 2016 at 10:04:58PM -0800, Joe Julian wrote:<br>
>> Does this mean race conditions are in master and are just being retried until they're not hit?<br>
>><br>
>> On November 13, 2016 9:33:51 PM PST, Nithya Balachandran <<a href="mailto:nbalacha@redhat.com" target="_blank">nbalacha@redhat.com</a>> wrote:<br>
>> >Hi,<br>
>> ><br>
>> >Our smoke tests have been failing quite frequently of late. While<br>
>> >re-triggering smoke several times in order to get a +1 works<br>
>> >eventually,<br>
>> >this does not really help anything IMO.<br>
>> ><br>
>> >I believe Jeff has already proposed this earlier but can we remove the<br>
>> >failing dbench tests from smoke until we figure out what is going on?<br>
><br>
> --<br>
> nigelb<br>
</div></div>> ______________________________<wbr>_________________<br>
<span>> Gluster-devel mailing list<br>
> <a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
> <a href="http://www.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://www.gluster.org/mailman<wbr>/listinfo/gluster-devel</a><br>
</span>______________________________<wbr>_________________<br>
<div class="m_4785646050033083736HOEnZb"><div class="m_4785646050033083736h5">Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://www.gluster.org/mailman<wbr>/listinfo/gluster-devel</a><br>
</div></div></blockquote></div></div></div><br></div></div>
<br>______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://www.gluster.org/<wbr>mailman/listinfo/gluster-devel</a><br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><br></div><div>~ Atin (atinm)<br></div></div></div></div>
</div></div>