<div dir="ltr">OK, i took it offline for now,<div>let me know if you see the issue again.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 6, 2016 at 2:09 PM, Tal Nisan <span dir="ltr"><<a href="mailto:tnisan@redhat.com" target="_blank">tnisan@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">Regardless, note that this specific Jenkins slave probably has an older JDK since it cannot work with 1.8<div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 6, 2016 at 1:40 PM, 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"><div>Thanks for reporting this, </div><div>Unfortunately Its a known issue without an easy fix. We are now moving all jobs from old jenkins to new one,</div><div>and find bugs is the last one that was left (dao tests was migrated to standard CI and should be merged soon, followed by disabling the jobs).</div><div><br></div><div>For now find bugs job will move to YAML and to the new jenkins soon (this week hopefully), and work will continue to move it to STD CI, which is more complex.</div><div><br></div><div>e.</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Mon, Jun 6, 2016 at 11:34 AM, Tal Nisan <span dir="ltr"><<a href="mailto:tnisan@redhat.com" target="_blank">tnisan@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><div dir="ltr">Check out this patch:<div><br></div><div><a href="https://gerrit.ovirt.org/#/c/58652/" target="_blank">https://gerrit.ovirt.org/#/c/58652/</a><br></div><div><br></div><div>Old Jenkins failed on Findbugs (seems like an env problem, not a findbugs analysis failure for that matter).</div><div>Patch was marked as failed CI yet as soon as the new Jenkins finished its run it overwritten the failed CI of the old Jenkins and marked as CI passed</div><div><br></div></div>
<br></div></div>_______________________________________________<br>
Infra mailing list<br>
<a href="mailto:Infra@ovirt.org" target="_blank">Infra@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/infra" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/infra</a><br>
<br></blockquote></div><span><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Eyal Edri<br>Associate Manager</div><div>RHEV DevOps<br>EMEA ENG Virtualization R&D<br>Red Hat Israel<br><br>phone: <a href="tel:%2B972-9-7692018" value="+97297692018" target="_blank">+972-9-7692018</a><br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div></div></div>
</font></span></div>
</blockquote></div><br></div>
</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>Eyal Edri<br>Associate Manager</div><div>RHEV 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>