> On 12 Apr 2017, at 12:10, Barak Korren <[email protected]> wrote: > > > > On 12 April 2017 at 12:44, Michal Skrivanek <[email protected] > <mailto:[email protected]>> wrote: > > 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 > > 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). > 'experimental' generally runs on the latest builds of all packages. > We're working on something that will allow blocking failed changes, but it > still some ways off (OVIRT-1077). > > btw, in the meantime, me and Tomas are working on narrowing down the original > failure. > > Is there a quick fix that could be put in place to get 'experimental' back to > work for everything else?
we finally managed to narrow it down and confirm the set of patches causing the problem on Saturday (had to work around the jsonrpc-java and some other stuff) engine artifacts[1] passed manual OST[2] now (and sorry Ido for aborting your job) patches should be taken in shortly Thanks, michal [1] http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64/3475/ <http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64/3475/> [2] http://jenkins.ovirt.org/job/ovirt-system-tests_manual/244 <http://jenkins.ovirt.org/job/ovirt-system-tests_manual/244> > > > -- > Barak Korren > [email protected] <mailto:[email protected]> > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ <https://ifireball.wordpress.com/>
_______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
