Hi, The branch is still broken and you are still merging more changes to it and increasing the chances of more regressions delaying your package build. I am once again asking you to stop merging to ovirt-engine master unless its a fix to the current regression. I trust the maintainers to be responsible and only merge changes that are meant to fix the current issue. https://gerrit.ovirt.org/#/q/status:merged+project:ovirt-engine+branch:ma... Thanks, Dafna On Tue, Nov 13, 2018 at 10:11 AM Dafna Ron <dron(a)redhat.com&gt; wrote: > Hi , > > Please stop merging to ovirt-engine master branch as we have been failing > on different regressions for the last 11 days. > > I do not want any other regressions to be introduced until we can > properly catch them which means we need to fix the current issues before > merging more changes. > > Thanks, > Dafna > > > > _______________________________________________ Infra mailing list -- infra(a)ovirt.org To unsubscribe send an email to infra-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/OKD4RRNU6PD...

On 14 Nov 2018, at 12:18, Eyal Edri <eedri(a)redhat.com&gt; wrote: I suggest to block merging on Gerrit until this is resolved. Otherwise, we can't guarantee how long it will take to fix it and get a working build. the best way out is to revert if we are confident about the offending patch. Dominik seems to found it, we’ll see once we get a green OST. There seems to be infra issues too, so hard to say, but if [1] passes the safest is to commit the revert [1] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/3507/ On Wed, Nov 14, 2018, 11:46 Dafna Ron <dron(a)redhat.com wrote: > Hi, > > The branch is still broken and you are still merging more changes to it > and increasing the chances of more regressions delaying your package build. > > I am once again asking you to stop merging to ovirt-engine master unless > its a fix to the current regression. > > I trust the maintainers to be responsible and only merge changes that are > meant to fix the current issue. > > > https://gerrit.ovirt.org/#/q/status:merged+project:ovirt-engine+branch:ma... > > Thanks, > Dafna > > > > On Tue, Nov 13, 2018 at 10:11 AM Dafna Ron <dron(a)redhat.com&gt; wrote: > >> Hi , >> >> Please stop merging to ovirt-engine master branch as we have been >> failing on different regressions for the last 11 days. >> >> I do not want any other regressions to be introduced until we can >> properly catch them which means we need to fix the current issues before >> merging more changes. >> >> Thanks, >> Dafna >> >> >> >> _______________________________________________ > Infra mailing list -- infra(a)ovirt.org > To unsubscribe send an email to infra-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/OKD4RRNU6PD... > _______________________________________________ Infra mailing list -- infra(a)ovirt.org To unsubscribe send an email to infra-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/WLH6BF3ZW7W...