On 19/08/14 09:33, Matthias Klose wrote:
[Nikolaus Rath wrote:]
>> That's a bug in the test (race condition) rather than in the program.
>> It's fixed upstream.
>
> [...] If you don't care
> about the autopkg tests, and if you are not ready to fix these but rather wait
> for the fixes from upstream (and maybe new bugs), then I think it's better to
> drop the autopkg tests.
There are always at least two possible reasons for a failing test: "the
code under test is wrong" or "the test is wrong".
The most important thing is that someone with knowledge of the package
has looked at the failure report and triaged it, i.e. assigned it an
appropriate priority based on their knowledge of the package. It appears
Nikolaus has done this, and it will be dealt with when it's dealt with.
I don't think there's a problem here.
S
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53f31a4b.1020...@debian.org
