Hi everyone,
I took offline the three el6 slaves
we had on
jenkins.ovirt.org:
el6-vm08.phx.ovirt.org
el6-vm09.phx.ovirt.org
el6-vm10.phx.ovirt.org
and enabled three el7 hosts instead:
el7-vm08.phx.ovirt.org
el7-vm09.phx.ovirt.org
el7-vm10.phx.ovirt.org
In the long run we might need to adjust the
job to use labels properly to not end up on el6.
Regards,
Evgheni Dereveanchin
----- Original Message -----
From: "Eyal Edri" <eedri(a)redhat.com>
To: "Barak Korren" <bkorren(a)redhat.com>, "Evgheni Dereveanchin"
<ederevea(a)redhat.com>
Cc: "infra" <infra(a)ovirt.org>, "Nir Soffer"
<nsoffer(a)redhat.com>
Sent: Friday, 1 July, 2016 9:17:28 AM
Subject: Re: 2 bugs in test setup
Evgheni, can you shut down the el6 slaves and power up fedora or el7
instead?
We should have enough powered off to reduce the load.
On Jul 1, 2016 9:50 AM, "Barak Korren" <bkorren(a)redhat.com> wrote:
בתאריך 1 ביולי 2016 01:54, "Nir Soffer" <nsoffer(a)redhat.com> כתב:
>
> Hi all,
>
> I noticed 2 bugs in the code setting up a test:
>
> 1. losetup is run with non-existent -D option
> 2. build does not fail although losetup failed
>
It seems the job ran on an el6 slave. My guess would be that '-D' works on
newer OSes (afk so can`t check atm). We should probably just drop the el6
slaves at this point. Mock should probably be enough to keep testing engine
on el6 for the 3.6 remaining life time.
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra