[ovirt-devel] oVirt CI now supports Fedora 27 and Fedora Rawhide

[Francesco Romani]

On 11/23/2017 04:23 PM, Nir Soffer wrote:
>
>
> On Thu, Nov 23, 2017 at 4:55 PM Dan Kenigsberg <danken at redhat.com
> <mailto:danken at redhat.com>> wrote:
>
>     On Thu, Nov 23, 2017 at 4:03 PM, Nir Soffer <nsoffer at redhat.com
>     <mailto:nsoffer at redhat.com>> wrote:
>     > On Thu, Nov 23, 2017 at 3:59 PM Dan Kenigsberg
>     <danken at redhat.com <mailto:danken at redhat.com>> wrote:
>     >>
>     >> On Thu, Nov 23, 2017 at 1:56 PM, Nir Soffer <nsoffer at redhat.com
>     <mailto:nsoffer at redhat.com>> wrote:
>     >> > On Thu, Nov 23, 2017 at 1:51 PM Edward Haas <ehaas at redhat.com
>     <mailto:ehaas at redhat.com>> wrote:
>     >> >>
>     >> >> Per what I see, all CI jobs on vdsm/fc27 fail.
>     >> >> This is the second time this week, please consider reverting.
>     >> >>
>     >> >> We should try to avoid such changed before the weekend
>     >> >
>     >> >
>     >> > Some of the failures like
>     >> >
>     >> >
>     http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc27-x86_64/100/console
>     >> >
>     >> > Should be fixed by:
>     >> > https://gerrit.ovirt.org/84569/
>     >> >
>     >> > I have see some network test failing when running mock_runner
>     locally,
>     >> > you may need to mark them as broken on fc27.
>     >>
>     >> We have a busy couple of weeks until release of ovirt-4.2.0. As
>     much
>     >> as I like consuming Fedora early, I'm not sure that enabling so
>     close
>     >> to the release was a good idea. Nothing forces us to do it now (and
>     >> there are a lot of reasons to do it later). Let's give it
>     another go,
>     >> but let us not keep it on the red for the weekend.
>     >
>     >
>     > I'm happy with the storage code being tested on current fedora.
>
>     I'm more than happy. I'm thrilled to for it to be tested and run.
>     I am not happy to give a vote to a job that was never ever successful.
>
>
> The job is successful, some tests or maybe the code they test need work.
> This is why we have skipif/xfail and broken_on_ci.
>  
>
>
>     >
>     > Please make sure the few failing network tests are not breaking
>     the build.
>
>     It's probably time to mark the tests that use loseup as
>     broken-on-jenkins
>
>
> loop devices are usually ok on jenkins. We have several tests in
> storage using
> them and I don't know about any failures. For example
> storage/blockdev_test.py.
>
> Francesco, do you want to mark them as broken for now?

Yes, because we don't have resource to spare to properly fix the tests.
Hopefully next week.


Bests,

-- 
Francesco Romani
Senior SW Eng., Virtualization R&D
Red Hat
IRC: fromani github: @fromanirh

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20171123/833b26df/attachment-0001.html>