<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Wed, Jan 17, 2018 at 5:08 PM Barak Korren <<a href="mailto:bkorren@redhat.com">bkorren@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Guys,<br>
<br>
I'm sure you are aware that 'ovirt-imageio' is currently failing to<br>
build on FC27 and Rawhide.<br></blockquote><div><br></div><div>Why are you sure? I never seen any build failure since we added the </div><div>fc27 and fcraw builds.</div><div><br></div><div>Please point us to failed builds.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I'm not sure you get the implications tough.<br>
<br>
The 1st thing that the release change-queue is checking, before<br>
running OST, is if all builds for all patches it is checking are<br>
building successfully for all platforms that the project has jobs for.<br>
<br>
This means that essentially no new 'ovirt-imageio' packages are making<br>
it into the tested and nightly repos for __any__ platform.<br>
<br>
Furthermore, with the way the system works for now, there is no<br>
special handling for build failures, with means they are treated like<br>
OST failures, which means the system runs an expensive bisection<br>
search to find the failing patch. So when your project fails to build,<br>
it slows down checking for other project's patches.<br>
<br>
I ask that you please do one of the following:<br>
1. Fix the FC27 and RAWHIDE builds<br>
2. Remove the FC27 and RAWHIDE build jobs<br>
3. Turn the FC27 and RAWHIDE build jobs into check-merged jobs which<br>
are not checked by the change-queue.<br>
<br>
--<br>
Barak Korren<br>
RHV DevOps team , RHCE, RHCi<br>
Red Hat EMEA<br>
<a href="http://redhat.com" rel="noreferrer" target="_blank">redhat.com</a> | TRIED. TESTED. TRUSTED. | <a href="http://redhat.com/trusted" rel="noreferrer" target="_blank">redhat.com/trusted</a><br>
</blockquote></div></div>