From: "Francesco Romani" <fromani(a)redhat.com>
To: "Eyal Edri" <eedri(a)redhat.com>
Cc: "Nir Soffer" <nsoffer(a)redhat.com>, "infra"
<infra(a)ovirt.org>, "Dan Kenigsberg" <danken(a)redhat.com>,
"Allon
Mureinik" <amureini(a)redhat.com>
Sent: Monday, June 9, 2014 3:03:13 PM
Subject: Re: Python segfault in while running vdsm unittests - first aid
----- Original Message ---
> From: "Eyal Edri" <eedri(a)redhat.com>
> To: "Nir Soffer" <nsoffer(a)redhat.com>
> Cc: "infra" <infra(a)ovirt.org>, "Dan Kenigsberg"
<danken(a)redhat.com>,
> "Francesco Romani" <fromani(a)redhat.com>, "Allon
> Mureinik" <amureini(a)redhat.com>
> Sent: Monday, June 9, 2014 1:54:24 PM
> Subject: Re: Python segfault in while running vdsm unittests - first aid
>
> > I can confirm what Francesco found - the failure is easily reproduced
> > (100%)
> > when running make check with the NOSE_WITH_XUNIT=1, and when using latest
> > nose version from git.
> >
> > This issue make the failing CI job not only useless, but harmful, wasting
> > everyone time.
> >
> > I suggest to remove the NOSE_WITH_XNUNIT flag until nose is fixed.
> >
>
> is there a bug open on nose, any newer version that has a fix for it?
Here is the bug:
https://github.com/nose-devs/nose/issues/817
No further activitity (neither on the bug nor on the repo) since my report
But I think this is a bug in python, either in the core or in the xml module
used by nose. nose probably only trigger the issue in the underlying
xml code written in c.