[Python-modules-team] Bug#853056: txfixtures: FTBFS randomly (failing tests)
Santiago Vila
sanvila at debian.org
Sun Jan 29 13:06:42 UTC 2017
Package: src:txfixtures
Version: 0.2.6-1
Severity: important
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 python2,python3 --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: python2.7 setup.py config
running config
I: pybuild base:184: python3.5 setup.py config
running config
dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python setup.py build
running build
running build_py
creating /<<PKGBUILDDIR>>/.pybuild/pythonX.Y_2.7/build/txfixtures
[... snipped ...]
test_reset_hung_thread (txfixtures.tests.test_reactor.ReactorTest)
txfixtures.tests.test_reactor.ReactorTest.test_reset_hung_thread ... ok
test_reset_thread_and_reactor_died (txfixtures.tests.test_reactor.ReactorTest)
txfixtures.tests.test_reactor.ReactorTest.test_reset_thread_and_reactor_died ... ok
test_reset_thread_died_but_reactor_is_running (txfixtures.tests.test_reactor.ReactorTest)
txfixtures.tests.test_reactor.ReactorTest.test_reset_thread_died_but_reactor_is_running ... ok
test_fail (txfixtures._twisted.tests.test_threading.InterruptableCallFromThreadTest)
txfixtures._twisted.tests.test_threading.InterruptableCallFromThreadTest.test_fail ... ok
test_success (txfixtures._twisted.tests.test_threading.InterruptableCallFromThreadTest)
txfixtures._twisted.tests.test_threading.InterruptableCallFromThreadTest.test_success ... ok
test_timeout (txfixtures._twisted.tests.test_threading.InterruptableCallFromThreadTest)
txfixtures._twisted.tests.test_threading.InterruptableCallFromThreadTest.test_timeout ... ok
======================================================================
ERROR: test_no_min_uptime (tests.test_service.ServiceProtocolIntegrationTest)
tests.test_service.ServiceProtocolIntegrationTest.test_no_min_uptime
----------------------------------------------------------------------
_StringException: Empty attachments:
fake-process
twisted-log
pythonlogging:'': {{{
Service process spawned
Service process exited: A process has ended with a probable error condition: process ended with exit code 1.
Give up waiting for the service to be ready: minimum uptime not yet elapsed
}}}
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/testtools/deferredruntest.py", line 206, in _log_user_exception
raise e
testtools.deferredruntest.UncleanReactorError: The reactor still thinks it needs to do things. Close all connections, kill all processes and make sure all delayed calls have either fired or been cancelled:
<twisted.internet.process.ProcessReader object at 0x7f4fb22c8e10>
<twisted.internet.process.ProcessWriter object at 0x7f4fb22c8c50>
<twisted.internet.process.ProcessReader object at 0x7f4fb22c8ed0>
----------------------------------------------------------------------
Ran 71 tests in 8.644s
FAILED (errors=1, skipped=2)
E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: cd /<<PKGBUILDDIR>>/.pybuild/pythonX.Y_2.7/build; python2.7 -m unittest discover -v
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:9: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
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/txfixtures/
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,
provided you try enough times (as the failure happens randomly).
Thanks.
More information about the Python-modules-team
mailing list