Source: pandas
Version: 1.1.4+dfsg-1
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).
Relevant part (hopefully):
> ==================== 18 passed, 121 skipped in 1.39 seconds
> ====================
> E: pybuild pybuild:353: test: plugin custom failed with: exit code=1:
> TEST_SUCCESS=true; cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build ; for
> TEST_SUBSET in /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/pandas/tests/* ;
> do LOCALE_OVERRIDE=C xvfb-run -a -s "-screen 0 1280x1024x24 -noreset"
> python3.9 -m pytest -s -v -m "not network and not slow" -k "not
> test_register_entrypoint"
> --confcutdir=/<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/pandas
> --deb-data-root-dir=/<<PKGBUILDDIR>>/pandas/tests --strict-data-files
> $TEST_SUBSET || test $? = 5 || TEST_SUCCESS=false ; done ; LOCALE_OVERRIDE=C
> python3.9 -m pytest -s -v -m "not network and not slow" --forked --runxfail
> --confcutdir=/<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/pandas
> --deb-data-root-dir=/<<PKGBUILDDIR>>/pandas/tests --strict-data-files
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/pandas/tests/groupby/transform/test_numba.py
>
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/pandas/tests/window/test_numba.py
>
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/pandas/tests/window/test_apply.py
> || true ; $TEST_SUCCESS
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.8
> 3.9" returned exit code 13
The full build log is available from:
http://qa-logs.debian.net/2020/12/05/pandas_1.1.4+dfsg-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!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.
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.
--
debian-science-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
