Hi All, Fcraw build on VDSM check-patch has been failing recently (again). fcraw cannot act as gating to the VDSM CI, as it is unstable (by definition). If there is a strong interest for some to track VDSM against this unstable distribution, it better be performed in parallel to the VDSM developing flow. With the current state, we are unable to trust the CI and it causes us to either overwrite its output (which I consider very bad) or just get stuck frequently. Could we please move this job to be triggered once a day as a nightly job and whoever is interested in its output to get notifications for it? Please. lets not make it a gating to VDSM development.

Thanks, Edy. _______________________________________________ Devel mailing list Devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/devel

2018-03-08 9:01 GMT+01:00 Eyal Edri <eedri(a)redhat.com&gt;: > > > On Thu, Mar 8, 2018 at 9:51 AM, Edward Haas <ehaas(a)redhat.com&gt; wrote: > >> Hi All, >> >> Fcraw build on VDSM check-patch has been failing recently (again). >> >> fcraw cannot act as gating to the VDSM CI, as it is unstable (by >> definition). >> If there is a strong interest for some to track VDSM against this >> unstable distribution, it better be performed in parallel to the VDSM >> developing flow. >> >> With the current state, we are unable to trust the CI and it causes us >> to either overwrite its output (which I consider very bad) or just get >> stuck frequently. >> >> Could we please move this job to be triggered once a day as a nightly >> job and whoever is interested in its output to get notifications for it? >> Please. lets not make it a gating to VDSM development. >> >> > +1 from me, I didn't see any real value from fcraw so far, especially if > it doesn't save us adding new fedora versions when they are out. > We should try to stabalize fc28 when its out. > I want just to note that not having fcraw working in the past means we won't be ready for fc28 when it will be out. Not having fcraw now means we won't be ready for fc29 and so on for all the future fedora versions. This means we won't be able to support fedora in a reliable way.

> > Also, CI team won't be adding nightly jobs for projects on demand on > production system, you're welcome to test it on your local env if needed. > > >> Thanks, >> Edy. >> >> _______________________________________________ >> Devel mailing list >> Devel(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/devel >> > > > > -- > > Eyal edri > > > MANAGER > > RHV DevOps > > EMEA VIRTUALIZATION R&D > > > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 <+972%209-769-2018> > irc: eedri (on #tlv #rhev-dev #rhev-integ) > > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>