[PKG-Openstack-devel] Bug#923827: python-zake: FTBFS randomly (failing tests)

[Thomas Goirand]

On 3/5/19 8:09 PM, Santiago Vila wrote:
> Package: src:python-zake
> Version: 0.2.2-2
> Severity: important
> Tags: ftbfs
> 
> Dear maintainer:
> 
> I tried to build this package in buster but it failed:
> 
> --------------------------------------------------------------------------------
> [...]
>  debian/rules build-indep
> pyversions: missing X(S)-Python-Version in control file, fall back to debian/pyversions
> pyversions: missing debian/pyversions file, fall back to supported versions
> py3versions: no X-Python3-Version in control file, using supported versions
> dh build-indep --buildsystem=python_distutils --with python2,python3
>    dh_update_autotools_config -i -O--buildsystem=python_distutils
>    dh_auto_configure -i -O--buildsystem=python_distutils
> dh_auto_configure: Please use the third-party "pybuild" build system instead of python-distutils
> dh_auto_configure: This feature will be removed in compat 12.
>    dh_auto_build -i -O--buildsystem=python_distutils
> dh_auto_build: Please use the third-party "pybuild" build system instead of python-distutils
> dh_auto_build: This feature will be removed in compat 12.
> pyversions: missing X(S)-Python-Version in control file, fall back to debian/pyversions
> pyversions: missing debian/pyversions file, fall back to supported versions
> 	python setup.py build --force
>    debian/rules override_dh_auto_test
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> pyversions: missing X(S)-Python-Version in control file, fall back to debian/pyversions
> pyversions: missing debian/pyversions file, fall back to supported versions
> py3versions: no X-Python3-Version in control file, using supported versions
> set -ex && for i in 2.7 3.7 ; do \
> 	PYTHON=python$i python$i -m nose -v --exclude-test=zake.tests.test_client.TestClient.test_child_watch_no_create ; \
> done
> + PYTHON=python2.7 python2.7 -m nose -v --exclude-test=zake.tests.test_client.TestClient.test_child_watch_no_create
> zake.tests.test_client.TestClient.test_child_child_watch ... ok
> zake.tests.test_client.TestClient.test_child_left_delete ... ok
> zake.tests.test_client.TestClient.test_child_watch ... ok
> zake.tests.test_client.TestClient.test_command ... ok
> zake.tests.test_client.TestClient.test_command_custom_version ... ok
> zake.tests.test_client.TestClient.test_command_empty_version ... ok
> zake.tests.test_client.TestClient.test_command_envi ... ok
> zake.tests.test_client.TestClient.test_command_no_connect ... ok
> zake.tests.test_client.TestClient.test_command_version ... ok
> zake.tests.test_client.TestClient.test_concurrent_restart ... ok
> zake.tests.test_client.TestClient.test_concurrent_transaction_aborts ... ok
> zake.tests.test_client.TestClient.test_concurrent_transaction_half_work ... ok
> zake.tests.test_client.TestClient.test_connected ... ok
> zake.tests.test_client.TestClient.test_create ... ok
> zake.tests.test_client.TestClient.test_create_async ... ok
> zake.tests.test_client.TestClient.test_create_async_exception ... ok
> zake.tests.test_client.TestClient.test_create_async_linked ... ok
> zake.tests.test_client.TestClient.test_create_sequence ... ok
> zake.tests.test_client.TestClient.test_create_slashed ... ok
> zake.tests.test_client.TestClient.test_data_watch ... ok
> zake.tests.test_client.TestClient.test_data_watch_not_triggered ... ok
> zake.tests.test_client.TestClient.test_delete ... ok
> zake.tests.test_client.TestClient.test_ephemeral_no_children ... ok
> zake.tests.test_client.TestClient.test_ephemeral_raises ... ok
> zake.tests.test_client.TestClient.test_exists ... ok
> zake.tests.test_client.TestClient.test_get_children ... ok
> zake.tests.test_client.TestClient.test_make_path ... ok
> zake.tests.test_client.TestClient.test_missing_leading_slash ... ok
> zake.tests.test_client.TestClient.test_no_make_path ... ok
> zake.tests.test_client.TestClient.test_path_normalization ... ok
> zake.tests.test_client.TestClient.test_recursive_delete ... ok
> zake.tests.test_client.TestClient.test_root ... ok
> zake.tests.test_client.TestClient.test_root_delete ... ok
> zake.tests.test_client.TestClient.test_sequence ... ok
> zake.tests.test_client.TestClient.test_session_id ... ok
> zake.tests.test_client.TestClient.test_sync ... ok
> zake.tests.test_client.TestClient.test_transaction ... ok
> zake.tests.test_client.TestClient.test_transaction_abort ... ok
> zake.tests.test_client.TestClient.test_transaction_check ... ok
> zake.tests.test_client.TestClient.test_version ... ok
> zake.tests.test_client.TestMultiClient.test_clients_attached ... ok
> zake.tests.test_client.TestMultiClient.test_clients_counter ... ok
> zake.tests.test_client.TestMultiClient.test_clients_triggered ... ok
> zake.tests.test_client.TestMultiClient.test_purge_clients_triggered ... FAIL
> 
> ======================================================================
> FAIL: zake.tests.test_client.TestMultiClient.test_purge_clients_triggered
> ----------------------------------------------------------------------
> _StringException: Traceback (most recent call last):
>   File "/<<PKGBUILDDIR>>/zake/tests/test_client.py", line 611, in test_purge_clients_triggered
>     self.assertTrue(fff_rcv.wait(WAIT_TIME))
>   File "/usr/lib/python2.7/dist-packages/unittest2/case.py", line 702, in assertTrue
>     raise self.failureException(msg)
> AssertionError: False is not true
> 
> 
> ----------------------------------------------------------------------
> Ran 44 tests in 60.543s
> 
> FAILED (failures=1)
> make[1]: *** [debian/rules:17: override_dh_auto_test] Error 1
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> make: *** [debian/rules:10: build-indep] Error 2
> dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2
> --------------------------------------------------------------------------------
> 
> The build was made in one of my autobuilders with "dpkg-buildpackage -A".
> 
> The failure happens randomly, i.e. sometimes it fails, sometimes it does not,
> so I don't have a "recipe" to reproduce it as such, but the "randomness"
> is reproducible in my autobuilders (i.e. when I build it a lot of times,
> there are always some failed builds).
> 
> I've put several failed build logs here for reference:
> 
> https://people.debian.org/~sanvila/build-logs/python-zake/
> 
> If you need a test machine to reproduce this, please contact me
> privately and I could provide ssh access to a machine where it happens
> (caveat: randomly and maybe with low probability).
> 
> 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 BTS web page for this package.
> 
> Thanks.

Hi Santiago,

Sorry I've let this slip without a reply.

Does the issue always appears in the same test? If so, then probably
just blacklist this unit test would do?

Cheers,

Thomas Goirand (zigo)