<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 27, 2016 at 12:39 PM, Nigel Babu <span dir="ltr"><<a href="mailto:nigelb@redhat.com" target="_blank">nigelb@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Tue, Sep 27, 2016 at 12:00:40PM +0530, Pranith Kumar Karampuri wrote:<br>
> On Tue, Sep 27, 2016 at 11:20 AM, Nigel Babu <<a href="mailto:nigelb@redhat.com">nigelb@redhat.com</a>> wrote:<br>
><br>
> > These are gbench failures rather than smoke failures. If you know how to<br>
> > debug dbench failures, please add comments on the bug and I'll get you the<br>
> > logs you need.<br>
> ><br>
><br>
> Oh, we can't archive the logs like we do for regression runs?<br>
<br>
</span>We don't log anything for smoke tests. Perhaps we should. Would you care to<br>
send a patch for smoke.sh[1] so we log the appropriate files?<br></blockquote><div><br></div><div>hmm... I see that gluster is launched normally so it should log fine. I guess I didn't understand the question.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
[1]: <a href="https://github.com/gluster/glusterfs-patch-acceptance-tests/blob/master/smoke.sh" rel="noreferrer" target="_blank">https://github.com/gluster/<wbr>glusterfs-patch-acceptance-<wbr>tests/blob/master/smoke.sh</a><br>
<br>
--<br>
nigelb<br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Pranith<br></div></div>
</div></div>