Your message dated Fri, 29 Jul 2011 12:25:41 +0200
with message-id <20110729102541.ga4...@vernstok.nl>
and subject line Fixed in bzr 2.4.0~beta5-3
has caused the Debian Bug report #631885,
regarding bzr: FTBFS: test suite fails on i386, armel, and mipsel
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.)
--
631885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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).
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!
--- End Message ---
--- Begin Message ---
Version: 2.4.0~beta5-3
These tests were fixed in the newer upstream release 2.4.0~beta5
--- End Message ---
