On Wed, Apr 12, 2017 at 12:10 PM, Barak Korren <[email protected]> wrote:
> > > On 12 April 2017 at 12:44, Michal Skrivanek <[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. > This sounds like using snapshots and we moved away from them to relay on versions. I do not want other people to use my changes if I do not specify so in the engine spec and pom. Please make sure to use only tagged version. > 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? > > > -- > Barak Korren > [email protected] > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ >
_______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
