<div dir="ltr"><div dir="auto"><div><br><div class="gmail_extra"><br><div class="gmail_quote">בתאריך 23 בדצמ׳ 2016 12:46 PM, "Dan Kenigsberg" <<a target="_blank" href="mailto:danken@redhat.com">danken@redhat.com</a>> כתב:<br type="attribution"><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail-m_-906957687266659890quote"><div class="gmail-m_-906957687266659890quoted-text">On Thu, Dec 22, 2016 at 5:45 PM, Yaniv Bronheim <<a target="_blank" href="mailto:ybronhei@redhat.com">ybronhei@redhat.com</a>> wrote:<br>
> On Thu, Dec 22, 2016 at 5:39 PM, Leon Goldberg <<a target="_blank" href="mailto:lgoldber@redhat.com">lgoldber@redhat.com</a>> wrote:<br>
><br>
>> Doesn't seem related; the patch does nothing but move pieces around.<br>
>><br>
>> Judging by the title I guess you're referring to<br>
>> <a target="_blank" rel="noreferrer" href="https://gerrit.ovirt.org/#/c/67787/">https://gerrit.ovirt.org/#/c/6<wbr>7787/</a> ?<br>
>><br>
><br>
><br>
> no.. you can see that after this patch it used to work (check the jobs<br>
> after the merge)<br>
> so something in <a target="_blank" rel="noreferrer" href="https://gerrit.ovirt.org/#/c/68078/">https://gerrit.ovirt.org/#/c/6<wbr>8078/</a> broke it<br>
<br>
</div>"post hoc ergo propter hoc" is a fallacy.<br>
<br>
We had a horrible week CI-wise; check-merged keept failing due to<br>
"Groovy thread" exception which is an internal Jenkins thingy. </blockquote></div></div></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">Please give the CI team the credit of being able to eliminate the Jenkins and environment related issues. We have runs that pre-date this week's issues and still show that behaviour. for example:<br><br><a href="http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/692/console">http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/692/console</a><br><br></div><div dir="auto">The fact that the job crashes during the groovy code is not an indicator that the issue is in that code. That exact same code runs for every single job in the system without failing, so it means that something in this job probably creates conditions that prevent it from running.<br><br></div><div dir="auto">Actually we know more then that. Looking carefully at the job logs you can see the groovy fails to run because the slave disconnects just before Jenkins tries to run it (By now you should be familiar with OVIRT-938). Again, all the CI code that runs before, after and during this job is also used in other jobs that do not fail in the same manner - With this I want to Yaniv to ask him to help figuring out if the check_merged.sh code may be doing anything that may cause this. Our conversation led to this email.<br></div><div dir="auto"><br></div><div dir="ltr">Trying to wave this this as a "Groovy failure" at this point is not helping. The CI team is not going to come up with a magic solution to this one without you guys` help.<br></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail-m_-906957687266659890quote">Now<br>
that's over, but a recent test failed on<br>
<br>
<a target="_blank" rel="noreferrer" href="http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/778/console">http://jenkins.ovirt.org/job/v<wbr>dsm_master_check-merged-el7-x8<wbr>6_64/778/console</a><br>
<br>
11:55:54 RuntimeError: Failed to run reposync 3 times for repoid:<br>
ovirt-master-snapshot-static-e<wbr>l7, aborting.<br>
<br>
It is wrong to pick up on the first patch that happened to see the<br>
"Groovy thread" exception.<br></blockquote></div></div></div></div>
</div>