Yes, there are 2 ways: 1) wait to a CQ run and then adds the 2 patches to run afterwards 2) run 1 patch that will fail, and then add to the queue at the same time the second patch and it should pass on the 2nd run.
On Tue, Jul 3, 2018 at 12:26 PM Martin Perina <mper...@redhat.com> wrote: > > > On Tue, Jul 3, 2018 at 11:03 AM, Ehud Yonasi <eyon...@redhat.com> wrote: > >> Suspected patch: >> >> https://gerrit.ovirt.org/#/c/91555/ >> >> Link to job: >> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8542/ >> >> Link to all logs: >> >> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8542/artifact/exported-artifacts/ >> >> Relevant error snippet: >> >> Error: ovirt-engine-wildfly-overlay conflicts with >> ovirt-engine-wildfly-13.0.0-1.el7.x86_64 >> >> > OK, I thought that I can do stepped approach: > > 1. Push ovirt-engine-wildfly-13 RPM into the repos > 2. Push ovirt-engine-wildfly-overlay-13 RPM, which requires > ovirt-engine-wildfly-13, into repos > > But it seems that due to serial nature of our CQ it's not possible, so can > we pass both patches [1] and [2] though CQ at once? > > Thanks > > Martin > > [1] > > https://gerrit.ovirt.org/#/c/91555/ > [2] https://gerrit.ovirt.org/#/c/91556/ > > > > -- > Martin Perina > Associate Manager, Software Engineering > Red Hat Czech s.r.o. >
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-le...@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/devel@ovirt.org/message/OFF7WQ4VLKSXBUO76LULG4ZWSNPKWBYB/
