<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 12 April 2017 at 12:44, Michal Skrivanek <span dir="ltr"><<a href="mailto:michal.skrivanek@redhat.com" target="_blank">michal.skrivanek@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 style="word-wrap:break-word"><div><span class=""><div><br></div></span>Well, Im not sure who’s handling that exactly, but vdsm-jsonrpc-java is getting into OST runs despite the OST failing since Saturday. That should not happen</div></div></blockquote><div><br></div><div>There is no mechanism for blocking stuff from going into 'experimental' ATM (Please differentiate between the 'experimental' flow that automates the testing and the OST which is the set of testing tools that can be used in various configurations).<br></div><div>'experimental' generally runs on the latest builds of all packages.<br>We're working on something that will allow blocking failed changes, but it still some ways off (OVIRT-1077).<br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>btw, in the meantime, me and Tomas are working on narrowing down the original failure.</div></div></blockquote><div><br></div><div>Is there a quick fix that could be put in place to get 'experimental' back to work for everything else?<br></div><div><br> </div></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Barak Korren<br><a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a><br>RHCE, RHCi, RHV-DevOps Team<br><a href="https://ifireball.wordpress.com/" target="_blank">https://ifireball.wordpress.com/</a></div>
</div></div>