Re: Jenkins failing on fcraw

Description

Adding infra-support to track this.
Evgheni, can you have a look to see if its something on infra side?

On Thu, Dec 21, 2017 at 2:10 PM, Milan Zamazal <mzamazal@redhat.com> wrote:

> Hi, I experienced CI -1 on https://gerrit.ovirt.org/#/c/85669/1 due to
> failing fcraw test. I can see that it's due to some broken package
> dependencies on that system. I've heard that fcraw should run the tests
> but not vote, however it put -1 score on the patch. Could it be fixed
> please?
>
> Thanks,
> Milan
> _______________________________________________
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>
>

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
irc: eedri (on #tlv #rhev-dev #rhev-integ)

Activity

Show:
Barak Korren
December 21, 2017, 12:48 PM

On 21 December 2017 at 14:31, Eyal Edri <eedri@redhat.com> wrote:

> Adding infra-support to track this.
> Evgheni, can you have a look to see if its something on infra side?
>

This is not on the infra side, it looks like the issue is when installing
packages specified in the *.packages file of vdsm.

It looks like some of the packages that are in the 'virt-preview' repo that
is configure in the *.repos file in vdsm are incompatible with rawhide.

I suppose that rawhide-combatible *.packages and *.repos files need to be
created for vdsm.

On Thu, Dec 21, 2017 at 2:10 PM, Milan Zamazal <mzamazal@redhat.com> wrote:
>
>> Hi, I experienced CI -1 on https://gerrit.ovirt.org/#/c/85669/1 due to
>> failing fcraw test. I can see that it's due to some broken package
>> dependencies on that system. I've heard that fcraw should run the tests
>> but not vote, however it put -1 score on the patch. Could it be fixed
>> please?
>>
>>
There in nothing to "fix" here, there is no such thing as a non-voting job
ATM. What you've heared is something Danken ask for, but we did not
implement that, it remains an RFE at this point...


Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

Milan Zamazal
December 21, 2017, 1:19 PM

I see, thank you for explanation. However I don't understand why it was
added to CI when it's not working.

Hm, is rawhide considered reliable and stable enough not to break CI
from time to time then?

Barak Korren
December 21, 2017, 3:22 PM

I see, thank you for explanation. However I don't understand why it was
added to CI when it's not working.

There was a thread to add fc27/fcraw jobs for various projects going on a couple of weeks ago, and as part of that work added the jobs for vdsm. I guess merging that before all dependencies were met was not the best decision, though I assumed the maintainers that approved it knew what they were doing...

Hm, is rawhide considered reliable and stable enough not to break CI
from time to time then?

It more that we WANT it to break CI to find issues before they reach the released versions... But some work is needed to ensure it at least works the 1st time...

Eyal Edri
December 26, 2017, 12:15 PM

vdsm fcraw jobs were disabled.
If at some point maintainers want to enable it, it should be done only after its verified to be working.

Assignee

infra

Reporter

Eyal Edri

Blocked By

None

Priority

Medium
Configure