Your message dated Wed, 9 Dec 2015 11:25:33 -0200
with message-id <[email protected]>
and subject line Re: Bug#798066: Multiarch-renamed python extensions not found
during autopkgtest testing
has caused the Debian Bug report #798066,
regarding autopkgtest: adt-run doesn't find multiarch-renamed Cython compiled
libraries
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 [email protected]
immediately.)
--
798066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798066
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: autopkgtest
Version: 3.6jessie1
Severity: normal
Tests fail on Python packages that have Cython-compiled modules. See,
for example, the test log for python-cobra on DebCI [1]. The tests there
fail with the error "solver not found", where the solver is the Cython-compiled
module that has been renamed for multiarch during the package build. However,
those tests are successful when manually installing the package and running the
tests in an updated Unstable chroot.
As another example, one test for python-pysam fails because it can't find
a compiled module [2]:
ERROR: Failure: ImportError (Building module _compile_test failed:
["CompileError: command 'x86_64-linux-gnu-gcc' failed with exit status 1\n"])
The problem was worked-around with a hack in the test run script where a
symlink is created to point to the multiarch-renamed library [3].
I have not tested with the latest version of adt-run, but the problem affects
Stable and the version running on DebianCI. I believe the problem is with this
package because the tests are fine when run manually after installation, even
in a clean chroot.
Many thanks and regards
Afif
1.
http://ci.debian.net/data/packages/unstable/amd64/p/python-cobra/20150822_180643.autopkgtest.log.gz
2.
http://ci.debian.net/data/packages/unstable/amd64/p/python-pysam/20150806_192500.autopkgtest.log.gz
3.
https://anonscm.debian.org/cgit/debian-med/python-pysam.git/tree/debian/tests/run-nose-tests?id=2334c5dec618182d106b2c8ac3042118491ca69b
-- System Information:
Debian Release: 8.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/12 CPU cores)
Locale: LANG=ar_SA.UTF-8, LC_CTYPE=ar_SA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages autopkgtest depends on:
ii apt-utils 1.0.9.8
ii libdpkg-perl 1.17.25
ii procps 2:3.3.9-9
ii python3 3.4.2-2
ii python3-debian 0.1.27
Versions of packages autopkgtest recommends:
ii autodep8 0.1
Versions of packages autopkgtest suggests:
pn lxc <none>
ii qemu-system 1:2.1+dfsg-12+deb8u1
ii qemu-utils 1:2.1+dfsg-12+deb8u1
ii schroot 1.6.10-1+b1
-- no debconf information
--- End Message ---
--- Begin Message ---
Control:
On Tue, Dec 08, 2015 at 11:25:47PM -0800, Afif Elghraoui wrote:
> Hi, debian-python,
>
> For Debian Med's python packages that have compiled extensions, I
> noticed that test suites run via autopkgtest fail because the package
> cannot find those extensions, as they've been renamed with the multiarch
> triplet.
>
> It seems to only be a problem with autopkgtest because I have in one
> case manually installed such a package and successfully ran its test
> suite. I therefore reported #798066 [1] against autopkgtest, but quite
> some time has elapsed since then and I'd like to get this resolved.
>
> Does anyone know why this might be the case? Autopkgtest for these
> packages is currently not very helpful because there are many spurious
> failures due to this issue. There are more details in my original bug
> report [1].
>
> Many thanks and regards
> Afif
>
> 1. http://bugs.debian.org/798066
autopkgtest does not do anything special wrt dependencies, it will
install exactly what you told it to in debian/tests/control (see the
spec¹ for reference), so I doubt this would be a problem with
autopkgtest.
¹
http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/tree/doc/README.package-tests.rst
I am therefore closing this bug.
--
Antonio Terceiro <[email protected]>
signature.asc
Description: PGP signature
--- End Message ---
