Re: Jenkins build failure due to "publish of test report" failing
----- Original Message -----
From: "Dan Kenigsberg" <danken(a)redhat.com>
To: "Eyal Edri" <eedri(a)redhat.com>
Cc: "Deepak C Shetty" <deepakcs(a)linux.vnet.ibm.com>, "Saggi
Mizrahi" <smizrahi(a)redhat.com>, "infra" <infra(a)ovirt.org>
Sent: Saturday, January 26, 2013 3:55:05 PM
Subject: Re: Jenkins build failure due to "publish of test report" failing
On Fri, Jan 25, 2013 at 01:36:42AM -0500, Eyal Edri wrote:
>
>
> ----- Original Message -----
> > 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.
Currently tests are failing because of nose not being installed on
the
slave. Only when nose exists it's time to blame danken.
i did exactly as saggi requested.
removed python-nose and installed python-nose1.1 (with symlink).
"""
from nose import config
ImportError: No module named nose
"""
http://jenkins.ovirt.org/job/vdsm_unit_tests_gerrit_el/75/console