<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Wed, Aug 8, 2018 at 2:28 PM Nigel Babu <<a href="mailto:nigelb@redhat.com">nigelb@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Wed, Aug 8, 2018 at 2:00 PM Ravishankar N <<a href="mailto:ravishankar@redhat.com" target="_blank">ravishankar@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
On 08/08/2018 05:07 AM, Shyam Ranganathan wrote:<br>
> 5) Current test failures<br>
> We still have the following tests failing and some without any RCA or<br>
> attention, (If something is incorrect, write back).<br>
><br>
> ./tests/basic/afr/add-brick-self-heal.t (needs attention)<br>
From the runs captured at <a href="https://review.gluster.org/#/c/20637/" rel="noreferrer" target="_blank">https://review.gluster.org/#/c/20637/</a> , I saw <br>
that the latest runs where this particular .t failed were at <br>
<a href="https://build.gluster.org/job/line-coverage/415" rel="noreferrer" target="_blank">https://build.gluster.org/job/line-coverage/415</a> and <br>
<a href="https://build.gluster.org/job/line-coverage/421/" rel="noreferrer" target="_blank">https://build.gluster.org/job/line-coverage/421/</a>.<br>
In both of these runs, there are no gluster 'regression' logs available <br>
at <a href="https://build.gluster.org/job/line-coverage/" rel="noreferrer" target="_blank">https://build.gluster.org/job/line-coverage/</a><build-number>/artifact. <br>
I have raised BZ 1613721 for it.</blockquote></div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"></blockquote><div><br></div><div>We've fixed this for newer runs, but we can do nothing for older runs, sadly.<br></div></div></div></blockquote><div>Thanks Nigel! I'm also blocked on this. The failures are not reproducible locally.</div><div>Without the logs we can not debug the issue. Will wait for the new runs to complete. </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_quote"><div></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Also, Shyam was saying that in case of retries, the old (failure) logs <br>
get overwritten by the retries which are successful. Can we disable <br>
re-trying the .ts when they fail just for this lock down period alone so <br>
that we do have the logs?</blockquote><div><br></div><div>Please don't apply a band-aid. Please fix run-test.sh so that the second run has a -retry attached to the file name or some such, please. <br></div></div></div>
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-devel</a></blockquote></div></div>