From: "Deepak C Shetty"
<deepakcs(a)linux.vnet.ibm.com>
To: "Eyal Edri" <eedri(a)redhat.com>
Cc: "Saggi Mizrahi" <smizrahi(a)redhat.com>, "infra"
<infra(a)ovirt.org>, "Dan Kenigsberg" <danken(a)redhat.com>
Sent: Friday, January 25, 2013 6:10:57 AM
Subject: Re: Jenkins build failure due to "publish of test report" failing
On 01/25/2013 12:36 AM, Eyal Edri wrote:
>
> ----- Original Message -----
>> From: "Saggi Mizrahi" <smizrahi(a)redhat.com>
>> To: "Eyal Edri" <eedri(a)redhat.com>, "Dan Kenigsberg"
>> <danken(a)redhat.com>
>> Cc: "infra" <infra(a)ovirt.org>, "Deepak C Shetty"
>> <deepakcs(a)linux.vnet.ibm.com>
>> Sent: Thursday, January 24, 2013 6:35:36 PM
>> Subject: Re: Jenkins build failure due to "publish of test report"
>> failing
>>
>> No, it will keep reporting failures.
>> This is because the EL hosts are misconfigured.
>>
>> Under RHEL 6 the python-nose package does not have the xunit
>> plugin.
>>
>> You need to remove it install the python-nose1.1 package and make
>> an
>> alias or alternatively make the makefile detect that nosetests is
>> missing and
>> call nosetests1.1 instead.
> ok, i installed nose1.1 on both el hosts, and added link to
> /usr/bin/nosetests.
Hi Eyal,
I still see the 'X' mark by jenkins for some of my patches as
below...
http://gerrit.ovirt.org/#/c/10196/
http://gerrit.ovirt.org/#/c/10195/
Wondering if the job was re-run for the above patches after the issue
was fixed ?
if it still has x, it means it wasn't fix.
please talk to saggi/danken for providing a fix for it.