[Python-modules-team] Bug#854701: python-asyncssh: FTBFS (failing tests)
Santiago Vila
sanvila at debian.org
Thu Feb 9 16:14:13 UTC 2017
Package: src:python-asyncssh
Version: 1.8.1-2
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:
--------------------------------------------------------------------------------
[...]
debian/rules build-indep
dh build-indep --with python3,sphinxdoc --buildsystem pybuild
dh_testdir -i -O--buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python3.5 setup.py config
running config
dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python3 setup.py build
running build
running build_py
creating /<<PKGBUILDDIR>>/.pybuild/pythonX.Y_3.5/build/asyncssh
copying asyncssh/agent_win32.py -> /<<PKGBUILDDIR>>/.pybuild/pythonX.Y_3.5/build/asyncssh
copying asyncssh/known_hosts.py -> /<<PKGBUILDDIR>>/.pybuild/pythonX.Y_3.5/build/asyncssh
[... snipped ...]
======================================================================
ERROR: test_xauth_environment (tests.test_x11._TestX11)
Test getting Xauthority path from the environment
----------------------------------------------------------------------
Traceback (most recent call last):
File "/usr/lib/python3.5/unittest/mock.py", line 1159, in patched
return func(*args, **keywargs)
File "/<<PKGBUILDDIR>>/tests/util.py", line 59, in async_wrapper
return self.loop.run_until_complete(wrapped_func)
File "/usr/lib/python3.5/asyncio/base_events.py", line 466, in run_until_complete
return future.result()
File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
raise self._exception
File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
result = coro.send(None)
File "/<<PKGBUILDDIR>>/tests/test_x11.py", line 498, in test_xauth_environment
yield from self._check_x11()
File "/<<PKGBUILDDIR>>/tests/test_x11.py", line 339, in _check_x11
proc = yield from _create_x11_process(conn, command, **kwargs)
File "/<<PKGBUILDDIR>>/tests/test_x11.py", line 52, in _create_x11_process
x11_display=x11_display, **kwargs))
File "/<<PKGBUILDDIR>>/asyncssh/misc.py", line 152, in __iter__
return (yield from self._coro)
File "/<<PKGBUILDDIR>>/asyncssh/connection.py", line 2487, in create_process
**kwargs)
File "/<<PKGBUILDDIR>>/asyncssh/connection.py", line 2408, in create_session
bool(self._agent_path)))
File "/<<PKGBUILDDIR>>/asyncssh/channel.py", line 895, in create
'X11 forwarding request failed')
asyncssh.misc.ChannelOpenError: Channel Open Error: X11 forwarding request failed
----------------------------------------------------------------------
Ran 638 tests in 268.661s
FAILED (errors=18, skipped=2)
Test failed: <unittest.runner.TextTestResult run=638 errors=18 failures=0>
error: Test failed: <unittest.runner.TextTestResult run=638 errors=18 failures=0>
E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: python3.5 setup.py test
dh_auto_test: pybuild --test -i python{version} -p 3.5 returned exit code 13
debian/rules:15: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
debian/rules:7: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
--------------------------------------------------------------------------------
This is just how the build ends, not necessarily the relevant part.
I've put several build logs here:
https://people.debian.org/~sanvila/build-logs/python-asyncssh/
If this is really a bug in one of the build-depends, please use reassign and affects,
so that this is still visible in the page for this package.
The bug should be reproducible with sbuild on a single CPU virtual machine.
If you could not reproduce this using sbuild on a single CPU virtual machine (as I did),
please do not downgrade or mark as unreproducible, I would then consider giving you access
to a virtual machine on which I can reproduce it so that you can as well.
(In such case, please contact me off-list for details).
Thanks.
More information about the Python-modules-team
mailing list