Source: python-skbio
Version: 0.5.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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):
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File
> "/<<PKGBUILDDIR>>/.pybuild/pythonX.Y_3.5/build/skbio/stats/tests/test_power.py",
> line 491, in test__identify_sample_groups_not_strict
> sorted(test_pairs.values()))
> File "/usr/lib/python3/dist-packages/pandas/indexes/base.py", line 3317, in
> _evaluate_compare
> raise ValueError('Lengths must match to compare')
> ValueError: Lengths must match to compare
>
> ----------------------------------------------------------------------
> Ran 2062 tests in 41.510s
>
> FAILED (SKIP=30, errors=15)
> sys:1: ResourceWarning: unclosed file <_io.TextIOWrapper name='/dev/null'
> mode='w' encoding='ANSI_X3.4-1968'>
> E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: cd
> /<<PKGBUILDDIR>>/.pybuild/pythonX.Y_3.5/build; python3.5 -m nose
> dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.5 returned
> exit code 13
> debian/rules:22: recipe for target 'override_dh_auto_test' failed
If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185
If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.
The full build log is available from:
http://aws-logs.debian.net/2016/10/21/python-skbio_0.5.0-1_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.
