<div dir="ltr"><div>Shwetha,</div><div><br></div><div>Is this time out configurable? Or is it hard-coded into the glusto-tests repo?<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Aug 26, 2017 at 1:59 AM, Shyam Ranganathan <span dir="ltr"><<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Nigel was kind enough to kick off a glusto run on 3.12 head a couple of days back. The status can be seen here [1].<br>
<br>
The run failed, but managed to get past what Glusto does on master (see [2]). Not that this is a consolation, but just stating the fact.<br>
<br>
The run [1] failed at,<br>
17:05:57 functional/bvt/test_cvt.py::Te<wbr>stGlusterHealSanity_dispersed_<wbr>glusterfs::test_self_heal_<wbr>when_io_in_progress FAILED<br>
<br>
The test case failed due to,<br>
17:10:28 E AssertionError: ('Volume %s : All process are not online', 'testvol_dispersed')<br>
<br>
The test case can be seen here [3], and the reason for failure is that Glusto did not wait long enough for the down brick to come up (it waited for 10 seconds, but the brick came up after 12 seconds or within the same second as the test for it being up. The log snippets pointing to this problem are here [4]. In short there was no real bug or issue that caused the failure as yet.<br>
<br>
Glusto as a gating factor for this release was desirable, but having got this far on 3.12 does help.<br>
<br>
@nigel, we could try post increasing the timeout between bringing the brick up to checking if it is up, and try another run, let me know if that works, and what is needed from me to get this going.<br>
<br>
Shyam<br>
<br>
[1] Glusto 3.12 run: <a href="https://ci.centos.org/view/Gluster/job/gluster_glusto/365/" rel="noreferrer" target="_blank">https://ci.centos.org/view/Glu<wbr>ster/job/gluster_glusto/365/</a><br>
<br>
[2] Glusto on master: <a href="https://ci.centos.org/view/Gluster/job/gluster_glusto/360/testReport/functional.bvt.test_cvt/" rel="noreferrer" target="_blank">https://ci.centos.org/view/Glu<wbr>ster/job/gluster_glusto/360/<wbr>testReport/functional.bvt.test<wbr>_cvt/</a><br>
<br>
[3] Failed test case: <a href="https://ci.centos.org/view/Gluster/job/gluster_glusto/365/testReport/functional.bvt.test_cvt/TestGlusterHealSanity_dispersed_glusterfs/test_self_heal_when_io_in_progress/" rel="noreferrer" target="_blank">https://ci.centos.org/view/Glu<wbr>ster/job/gluster_glusto/365/<wbr>testReport/functional.bvt.test<wbr>_cvt/TestGlusterHealSanity_dis<wbr>persed_glusterfs/test_self_hea<wbr>l_when_io_in_progress/</a><br>
<br>
[4] Log analysis pointing to the failed check: <a href="https://paste.fedoraproject.org/paste/znTPiFLrc2~vsWuoYRToZA" rel="noreferrer" target="_blank">https://paste.fedoraproject.or<wbr>g/paste/znTPiFLrc2~vsWuoYRToZA</a><br>
<br>
"Releases are made better together"<br>
______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-devel</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">nigelb<br></div></div>
</div>