Your message dated Thu, 09 Feb 2012 17:33:41 +0100
with message-id <4f33f565.5070...@debian.org>
and subject line Re: pyside: Too many build-tests failures (on some
architectures) - Maintainer testing-blocker RC bug
has caused the Debian Bug report #618347,
regarding pyside: Too many build-tests failures (on some architectures) -
Maintainer testing-blocker RC bug
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
618347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyside
Version: 1.0.0-2
Severity: serious
Justification: My quality treshold level
PySide currently has too many tests failing with tough errors (SIGILL,
SIGSEGV) on some architectures (ia64, sparc, armel).
Tests are currently set non critical (having compiled package helps
debugging), but they should be set critical to enter testing.
Hence this RC bug, forbidding pyside to enter testing.
-- System Information:
Debian Release: wheezy/sid
APT prefers squeeze-updates
APT policy: (500, 'squeeze-updates'), (500, 'unstable'), (500, 'testing'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38-rc6-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Version: 1.1.0-1
Le 14.03.2011 16:08, Didier Raboud a écrit :
> Justification: My quality treshold level
>
> PySide currently has too many tests failing with tough errors (SIGILL,
> SIGSEGV) on some architectures (ia64, sparc, armel).
I now changed my mind.
According to my latest automated analysis of the build logs of the
build-dependencies of pyside [0,1,2], none of them has tests that fail
in all release architectures. This doesn't mean there are no bugs, as
(as far as I know), their test suite doesn't provide full code coverage,
but this is still an indicator of good health.
The automated analysis of the pyside build log [3] reveals that a total
of 20 tests fail for various reasons across various architectures
(amongst a grand total of 405 tests). This means that at worse, 95% of
the tests work fine on all release architectures. Same as above, as the
tests don't cover the whole codebase, there are possibly other bugs.
I do now think that the benefits of providing the 1.1.0 version of
PySide in Wheezy overwhelms the at-worst-5% non-working parts of it.
(Which haven't /yet/ triggered bugs in the Debian BTS).
As a final note, the situation is different from Squeeze's as the PySide
codebase is now mostly stable and sees a less frenetic upgrade pace; I
don't expect much disruptive changes before Wheezy's freeze in June.
So I am hereby closing this bug as "fixed" in 1.1.0-1, allowing pyside
to enter testing.
Cheers,
OdyX
[0]
http://alioth.debian.org/~odyx-guest/packages/pyside/apiextractor_0.10.10-1_analysis.txt
[1]
http://alioth.debian.org/~odyx-guest/packages/pyside/generatorrunner_0.6.15-1_analysis.txt
[2]
http://alioth.debian.org/~odyx-guest/packages/pyside/shiboken_1.1.0-2_analysis.txt
[3]
http://alioth.debian.org/~odyx-guest/packages/pyside/pyside_1.1.0-1_analysis.txt
signature.asc
Description: OpenPGP digital signature
--- End Message ---
