<div dir="ltr">Looks like the problem was solved in a later patch [1].<br><br><a href="https://gerrit.ovirt.org/62373">https://gerrit.ovirt.org/62373</a><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 16, 2016 at 8:16 PM, Yevgeny Zaspitsky <span dir="ltr"><<a href="mailto:yzaspits@redhat.com" target="_blank">yzaspits@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">oops, the patch is that <a href="https://gerrit.ovirt.org/61891" target="_blank">https://gerrit.ovirt.org/61891</a><br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 16, 2016 at 7:12 PM, Yevgeny Zaspitsky <span dir="ltr"><<a href="mailto:yzaspits@redhat.com" target="_blank">yzaspits@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><div>Looks like [1] has added the very last line that was over the findBugs limit of reasonable file size.<br></div>Since that change was merged all consequence patches get -1 from CI.<br></div><br>We should either ignore that message in the findBugs configuration or fix that somehow. But letting CI nack the patch, then figure what's the nature of the failure and then ignore the nack doesn't seem very productive to me.<br><div><div><br>[1] <a href="https://gerrit.ovirt.org/#/c/62386/" target="_blank">https://gerrit.ovirt.org/#/c/6<wbr>2386/</a><br></div></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>