[Python-modules-team] Bug#887819: pyzmq FTBFS: TestAsyncioAuthentication.test_null failure

Luca Boccassi bluca at debian.org
Wed Apr 4 18:20:31 BST 2018


Control: reassign -1 libzmq5 4.2.3-1
Control: forwarded -1 https://github.com/zeromq/libzmq/pull/3018
Control: close -1 4.2.5-1

On Sat, 20 Jan 2018 09:40:31 +0200 Adrian Bunk <bunk at debian.org> wrote:
> Source: pyzmq
> Version: 16.0.2-2
> Severity: serious
> Tags: buster sid
> 
> Some recent change in unstable makes pyzmq FTBFS:
> 
> https://tests.reproducible-builds.org/debian/history/pyzmq.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/py
zmq.html
> 
> ...
> =================================== FAILURES
===================================
> _____________________ TestAsyncioAuthentication.test_null
______________________
> 
> self = <zmq.tests.asyncio._test_asyncio.TestAsyncioAuthentication
testMethod=test_null>
> 
>     def test_null(self):
>         """threaded auth - NULL"""
>         # A default NULL connection should always succeed, and not
>         # go through our authentication infrastructure at all.
>         self.auth.stop()
>         self.auth = None
>         # use a new context, so ZAP isn't inherited
>         self.context = self.Context()
>     
>         server = self.socket(zmq.PUSH)
>         client = self.socket(zmq.PULL)
>         self.assertTrue(self.can_connect(server, client))
>     
>         # By setting a domain we switch on authentication for NULL
sockets,
>         # though no policies are configured yet. The client
connection
>         # should still be allowed.
>         server = self.socket(zmq.PUSH)
>         server.zap_domain = b'global'
>         client = self.socket(zmq.PULL)
> >       self.assertTrue(self.can_connect(server, client))
> E       AssertionError: False is not true
> 
> zmq/tests/test_auth.py:131: AssertionError
> ----------------------------- Captured stderr call ------------------
-----------
> DEBUG:zmq.auth:Starting
> --------------------------- Captured stderr teardown ----------------
-----------
> ERROR:asyncio:Task was destroyed but it is pending!
> task: <Task pending coro=<AsyncioAuthenticator.__handle_zap() done,
defined at /build/1st/pyzmq-
16.0.2/.pybuild/pythonX.Y_3.6/build/zmq/auth/asyncio/__init__.py:25>
wait_for=<Future cancelled>>
> =============== 1 failed, 221 passed, 9 skipped in 32.51 seconds
===============
> E: pybuild pybuild:283: test: plugin distutils failed with: exit
code=1: cd /build/1st/pyzmq-16.0.2/.pybuild/pythonX.Y_3.6/build;
python3.6 -m pytest -v --ignore=zmq/tests/test_auth.py --
ignore=zmq/tests/test_security.py
> dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.6
--test-pytest returned exit code 13
> debian/rules:56: recipe for target 'override_dh_auto_test' failed
> make[1]: *** [override_dh_auto_test] Error 25

Hi,

This was a regression in libzmq5 4.2.3, fixed in 4.2.5 which is already
in sid/buster. Reassigning and closing for housekeeping.

https://github.com/zeromq/pyzmq/issues/1156
https://github.com/zeromq/libzmq/pull/3018

-- 
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/python-modules-team/attachments/20180404/73f7fdd9/attachment.sig>


More information about the Python-modules-team mailing list