Bug#755342: python-apt: FTBFS: Tests failures
Source: python-apt
Version: 0.9.3.8
Severity: serious
Tags: jessie sid
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20140718 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/«PKGBUILDDIR»'
> set -e; for python in python2.7 python3.4 ; do \
> $python tests/test_all.py -q || [ "linux" = "hurd" ]; \
> done;
> [tests] Running on 2.7.8 (default, Jul 4 2014, 13:08:34) [GCC 4.9.0]
> Using library_dir: '/«PKGBUILDDIR»/build/lib.linux-x86_64-2.7'WARNING: Failed to read mirror file
> WARNING: Failed to read mirror file
> WARNING: Failed to read mirror file
> WARNING: Failed to read mirror file
> WARNING: Failed to read mirror file
> WARNING: Failed to read mirror file
> WARNING: Failed to read mirror file
> WARNING: Failed to read mirror file
> ======================================================================
> FAIL: test_add_key_from_server_mitm (test_auth.TestAuthKeys)
> Verify that the key fingerprint is verified after download
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "/«PKGBUILDDIR»/tests/test_auth.py", line 216, in test_add_key_from_server_mitm
> cm.exception)
> AssertionError: recv from 'hkp://localhost:19191' failed for '0101010178F7FE5C3E65D8AF8B48AD6246925553'
>
> ----------------------------------------------------------------------
> Ran 88 tests in 25.897s
>
> FAILED (failures=1)
> debian/rules:43: recipe for target 'override_dh_auto_test' failed
> make[1]: *** [override_dh_auto_test] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/07/18/python-apt_0.9.3.8_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
Reply to: