Hi Aaron,
On 28/06/11 04:06, Aaron M. Ucko wrote:
Source: bzr
Version: 2.4.0~beta4-4
Severity: serious
Justification: fails to build from source
Builds of bzr hit test suite failures on three platforms (those running
Linux on 32-bit little-endian processors, FWIW). The i386 build failed in
bzrlib.tests.blackbox.test_branch.TestBranch.test_branch_broken_pack with
(AFAICT) 'branch a b' yielding status 0 rather than 3, and the armel and
mipsel builds failed with errors of the form
bzrlib.tests.test_smart_transport.ReadOnlyEndToEndTests.test_mkdir_error_readonly
is leaking threads among N leaking tests.
1 non-main threads were left active in the end.
(where N = 6 on armel and 5 on mipsel).
This is just a warning - the armel/mipsel build appears to be failing
because of a problem with expected failure handling.
Could you please take a look? It's possible that some of the failures
simply stem from glitches, in which case you can ask the autobuilders'
maintainers to requeue bzr. (I'm not involved with automatic builds
myself; I just noticed the failures because python-bzrlib-dbg showed up on
amd64 but not i386.)
Thanks for the bug report. The related upstream bug report is:
https://bugs.launchpad.net/bzr/+bug/803452
There is a merge proposal in progress which address the log issue.
Cheers,
Jelmer
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
