Source: python-pykka
Version: 2.0.2-6
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python3,sphinxdoc --buildsystem=pybuild
>    dh_update_autotools_config -O--buildsystem=pybuild
>    dh_autoreconf -O--buildsystem=pybuild
>    dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py config 
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
>    dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_pykka/build/pykka
> copying pykka/_threading.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_pykka/build/pykka
> copying pykka/_future.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_pykka/build/pykka
> copying pykka/gevent.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_pykka/build/pykka
> copying pykka/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_pykka/build/pykka
> copying pykka/debug.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_pykka/build/pykka
> copying pykka/_ref.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_pykka/build/pykka
> copying pykka/_actor.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_pykka/build/pykka
> copying pykka/messages.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_pykka/build/pykka
> copying pykka/_registry.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_pykka/build/pykka
> copying pykka/_envelope.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_pykka/build/pykka
> copying pykka/_proxy.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_pykka/build/pykka
> copying pykka/_exceptions.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_pykka/build/pykka
> copying pykka/eventlet.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_pykka/build/pykka
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_pykka/build/pykka/_compat
> copying pykka/_compat/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_pykka/build/pykka/_compat
> copying pykka/_compat/await_py3.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_pykka/build/pykka/_compat
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_pykka/build/pykka
> copying pykka/_threading.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_pykka/build/pykka
> copying pykka/_future.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_pykka/build/pykka
> copying pykka/gevent.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_pykka/build/pykka
> copying pykka/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_pykka/build/pykka
> copying pykka/debug.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_pykka/build/pykka
> copying pykka/_ref.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_pykka/build/pykka
> copying pykka/_actor.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_pykka/build/pykka
> copying pykka/messages.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_pykka/build/pykka
> copying pykka/_registry.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_pykka/build/pykka
> copying pykka/_envelope.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_pykka/build/pykka
> copying pykka/_proxy.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_pykka/build/pykka
> copying pykka/_exceptions.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_pykka/build/pykka
> copying pykka/eventlet.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_pykka/build/pykka
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_pykka/build/pykka/_compat
> copying pykka/_compat/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_pykka/build/pykka/_compat
> copying pykka/_compat/await_py3.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_pykka/build/pykka/_compat
>    dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_pykka/build; 
> python3.9 -m pytest -k "not noncallable_mock"
> ============================= test session starts 
> ==============================
> platform linux -- Python 3.9.0+, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
> rootdir: /<<PKGBUILDDIR>>
> plugins: mock-1.10.4
> collected 409 items / 3 deselected / 406 selected
> 
> tests/test_actor.py ...................                                  [  
> 4%]
> tests/test_future.py ......................                              [ 
> 10%]
> tests/test_future_py3.py ..                                              [ 
> 10%]
> tests/test_logging.py .......                                            [ 
> 12%]
> tests/test_ref.py .......................                                [ 
> 17%]
> tests/test_registry.py ............                                      [ 
> 20%]
> tests/proxy/test_attribute_access.py ........                            [ 
> 22%]
> tests/proxy/test_dynamic_method_calls.py ..                              [ 
> 23%]
> tests/proxy/test_legacy_message_format.py ..                             [ 
> 23%]
> tests/proxy/test_mocking.py ..                                           [ 
> 24%]
> tests/proxy/test_proxy.py .................                              [ 
> 28%]
> tests/proxy/test_static_method_calls.py ........                         [ 
> 30%]
> tests/proxy/test_traversable.py ......                                   [ 
> 32%]
> tests/test_actor.py Segmentation fault
> E: pybuild pybuild:352: test: plugin distutils failed with: exit code=139: cd 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_pykka/build; python3.9 -m pytest -k 
> "not noncallable_mock"
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 
> 3.8" returned exit code 13

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/python-pykka_2.0.2-6_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 via email to