<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Mar 19, 2017 at 10:33 AM, Eyal Edri <span dir="ltr"><<a href="mailto:eedri@redhat.com" target="_blank">eedri@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 Sun, Mar 19, 2017 at 10:30 AM, Oved Ourfali <span dir="ltr"><<a href="mailto:oourfali@redhat.com" target="_blank">oourfali@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">As Piotr mentioned, the job is using 1.3.8 however 1.3.9 was released.....</div></blockquote><div><br></div></span><div>Thanks, </div><div>We will look into the logs and find out what caused it to use 1.3.8 and report here on the results, can't be sure yet if its a bug in the job or anything else. </div></div></div></div></blockquote><div><br></div><div>Let me explain what happened:</div><div><br></div><div>1. check-patch jobs used to run on latest 'tested' repo, but that repo is very big as it contains history of all the builds done for a release [1]</div><div>2. recently we found a bug that caused OST to fail due to out of memory because it tried to sync the entire tested repo into memory ( that's how OST works ), so the tested repo was removed from check-patch.</div><div>3. This means that now check-patch is only using the repos in the reposync file, which for 4.1 is latest released. </div><div>4. vdsm-jsonrpc-java 1.3.9 wasn't released in any official oVirt 4.1 release, this is why the job used 1.3.8 which is the latest released.</div><div>5. We also don't want to replace the default repos for OST on 4.1 to something other than released, because the basic suite per release should always check against official release [2]</div><div>6. As a side note - manual jobs also support running on latest tested, so this issue is solely restricted to 'check-patch' jobs.</div><div><br></div><div>We do however believe that running check-patch on latest code is important, so we'll look into providing an alternate solution that won't break any of the above restrictions,</div><div>Suggestions are welcome of course. </div><div><br></div><div><br></div><div><br></div><div>[1] It is done so anyone that wants to check oVirt can do it w/o worrying that a pkg will be removed during testing ( something that was happening when used experimental lastest.tested repo )</div><div>[2] As opposed to experimental flows which DO check against latest code, which is why 4.1 experimental didn't fail on this issue, as it used 1.3.9</div><div><br></div><div> </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"><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="m_9016459783967119444h5">On Sun, Mar 19, 2017 at 10:27 AM, Barak Korren <span dir="ltr"><<a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_9016459783967119444h5"><div dir="auto"><div><br><div class="gmail_extra"><br><div class="gmail_quote">בתאריך 17 במרץ 2017 02:32 PM, "Piotr Kliczewski" <<a href="mailto:piotr.kliczewski@gmail.com" target="_blank">piotr.kliczewski@gmail.com</a>> כתב:<span><blockquote class="m_9016459783967119444m_-3331240927870797830m_7403498655202568278quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="m_9016459783967119444m_-3331240927870797830m_7403498655202568278quoted-text">
<br>
</div>The change was merged 2 weeks ago. How can we make sure not to waste<br>
people time next time to analyze the issue?<br>
<div class="m_9016459783967119444m_-3331240927870797830m_7403498655202568278elided-text"></div></blockquote></span></div></div></div><div dir="auto"><br></div><div dir="auto">"Merged" is hardly "released".</div><div dir="auto"><br></div><div dir="auto">As long as a fix does not make it to a release, users can still come across the issue, and so can OST. I can't think of a quick way to avoid that, but I'm open to suggestions....</div><div dir="auto"><br></div><div dir="auto">WRT getting more frequent oVirt releases, I'm hardly in a position to give input about that.</div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="m_9016459783967119444m_-3331240927870797830m_7403498655202568278quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="m_9016459783967119444m_-3331240927870797830m_7403498655202568278elided-text"><br>
</div></blockquote></div><br></div></div></div>
<br></div></div><span>______________________________<wbr>_________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/devel</a><br></span></blockquote></div><br></div>
<br>______________________________<wbr>_________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/devel</a><br></blockquote></span></div><br><br clear="all"><span class=""><div><br></div>-- <br><div class="m_9016459783967119444gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Eyal Edri<br>Associate Manager</div><div>RHV DevOps<br>EMEA ENG Virtualization R&D<br>Red Hat Israel<br><br>phone: <a href="tel:+972%209-769-2018" value="+97297692018" target="_blank">+972-9-7692018</a><br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div></div></div></div></div>
</span></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Eyal Edri<br>Associate Manager</div><div>RHV DevOps<br>EMEA ENG Virtualization R&D<br>Red Hat Israel<br><br>phone: +972-9-7692018<br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div></div></div></div></div>
</div></div>