On Fri, Feb 24, 2017 at 4:59 PM, Sandro Bonazzola <sbonazzo(a)redhat.com&gt; wrote: > Hi, > with the following commits: > - https://gerrit.ovirt.org/71553 > - https://gerrit.ovirt.org/71623 > > a minimal repository closure check is added to check-patches.sh. > Instead of performing a full blown repository closure, I limited the > check to the built rpms in oreder to reduce the risk of hitting repository > closure errors due to different projects. > > This should help dropping the long time failing repository closure jobs > which are struggling to keep the pace with the changes we introduce in > master. > It should also help avoiding to merge patches which will break the > repository and the plain rpm install flow. > Forgot to mention I recomend to steal the check for your own project reducing repository closure issues as well :-) > > The second patch switch from ovirt-master-release to experimental repo. > Here I need infra input, not sure experimental is the desired repo, > deisgned to replace ovirt-master-snapshot. > > Thanks, > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

OST come into play too late, with patch already merged and dep tree broken.

It will avoid the rpm to be published but it will fail the subsequent ost hiding other issues. Any suggestion on how to avoid it? Run OST in check patch?

I haven't merged the patches because I wanted feedback like this, thanks Barack.