On 15.03.2016 22:48, László Böszörményi (GCS) wrote: > On Tue, Mar 15, 2016 at 10:26 AM, Emilio Pozuelo Monfort > <po...@debian.org> wrote: >> On 14/03/16 22:03, Emilio Pozuelo Monfort wrote: >>> Looks good. No problem and thanks for reacting that fast! >> >> I scheduled the binNMUs last night and things are going well. The only issue >> seems to be pyzmq, see #818265. > This is known to pyzmq upstream[1] for about three years. It happens > on Ubuntu, Red Hat, CentOS and with ZeroMQ 4.0.x as well. While > timer_create() [4] is in librt, the standard GNU C library, it seems > pyzmq miss to link with it on the failing architectures. User reports > says that 'pip install pyzmq --install-option="--zmq=/usr/lib"' forces > the linking. I don't know how pass it to setup.py (not using pip > directly) and the path should be multiarch aware for us. > > Hope this helps, > Laszlo/GCS > [1] https://github.com/zeromq/pyzmq/issues/391 > [2] https://github.com/zeromq/pyzmq/issues/468 > [3] https://github.com/zeromq/pyzmq/issues/658 > [4] http://man7.org/linux/man-pages/man2/timer_create.2.html >
Are you saying linking against -lrt will fix the tests deadlocking? I don't quite see the relation between the hanging tests and the linked issues. The implicit declaration errors have always been there I think but only in a configure check so harmless (until now?).