pyzmq ftbfs on amd64 and i386 (test failures)

Bug #910757 reported by Matthias Klose
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libzeromq-perl (Ubuntu)
Fix Released
Undecided
Unassigned
pyzmq (Ubuntu)
Fix Released
High
Unassigned
zeromq (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

see https://launchpad.net/ubuntu/precise/+source/pyzmq/2.1.10-2

running test
test_init_iface (zmq.tests.test_log.TestPubLog) ... message
ok
test_init_socket (zmq.tests.test_log.TestPubLog) ... ERROR
ERROR
test_root_topic (zmq.tests.test_log.TestPubLog) ... ERROR
test_simple (zmq.tests.test_ioloop.TestIOLoop)
simple IOLoop creation test ... ok
test_timeout_compare (zmq.tests.test_ioloop.TestIOLoop)
test timeout comparisons ... ok
test_above_30 (zmq.tests.test_message.TestMessage)
Message above 30 bytes are never copied by 0MQ. ... ok
test_bad_buffer_in (zmq.tests.test_message.TestMessage)
test using a bad object ... ok
test_buffer_in (zmq.tests.test_message.TestMessage)
test using a buffer as input ... ok
test_buffer_numpy (zmq.tests.test_message.TestMessage)
test non-copying numpy array messages ... skipped 'requires numpy'
test_buffer_out (zmq.tests.test_message.TestMessage)
receiving buffered output ... ok
test_bytes (zmq.tests.test_message.TestMessage)
Test the Message.bytes property. ... ok
test_len (zmq.tests.test_message.TestMessage)
Test the len of the Messages. ... ok
test_lifecycle1 (zmq.tests.test_message.TestMessage)
Run through a ref counting cycle with a copy. ... ok
test_lifecycle2 (zmq.tests.test_message.TestMessage)
Run through a different ref counting cycle with a copy. ... ok
test_memoryview (zmq.tests.test_message.TestMessage)
test messages from memoryview ... ok
test_multi_tracker (zmq.tests.test_message.TestMessage) ... ok
test_multisend (zmq.tests.test_message.TestMessage)
ensure that a message remains intact after multiple sends ... ERROR
ERROR
test_no_tracker (zmq.tests.test_message.TestMessage) ... ok
test_noncopying_recv (zmq.tests.test_message.TestMessage)
check for clobbering message buffers ... ERROR
ERROR
test_str (zmq.tests.test_message.TestMessage)
Test the str representations of the Messages. ... ok
test_tracker (zmq.tests.test_message.TestMessage) ... ok
test_unicode (zmq.tests.test_message.TestMessage)
Test the unicode representations of the Messages. ... ok
test_callable_check (zmq.tests.test_zmqstream.TestZMQStream)
Ensure callable check works (py3k). ... ok
test_device_attributes (zmq.tests.test_device.TestDevice) ... ok
test_device_types (zmq.tests.test_device.TestDevice) ... ok
test_labels (zmq.tests.test_device.TestDevice)
test device support for SNDLABEL ... skipped 'Only for libzmq 3'
test_single_socket_forwarder_bind (zmq.tests.test_device.TestDevice) ... ERROR
ERROR
test_single_socket_forwarder_connect (zmq.tests.test_device.TestDevice) ... ERROR
test_tsdevice_attributes (zmq.tests.test_device.TestDevice) ... ok
test_basic_multipart (zmq.tests.test_multipart.TestMultipart) ... ERROR
ERROR
test_router_dealer (zmq.tests.test_multipart.TestMultipart) ... ERROR
test_strerror (zmq.tests.test_error.TestZMQError)
test that strerror gets the right type. ... ok
test_zmqerror (zmq.tests.test_error.TestZMQError) ... ok
test_basic (zmq.tests.test_pubsub.TestPubSub) ... ERROR
ERROR
test_topic (zmq.tests.test_pubsub.TestPubSub) ... ERROR
test_bad_send_recv (zmq.tests.test_reqrep.TestReqRep) ... ERROR
ERROR
test_basic (zmq.tests.test_reqrep.TestReqRep) ... ERROR
test_json (zmq.tests.test_reqrep.TestReqRep) ... ERROR
ERROR
test_large_msg (zmq.tests.test_reqrep.TestReqRep) ... ERROR
Assertion failed: pfd.revents & POLLIN (signaler.cpp:155)
nose unavailable, falling back on unittest. Skipped tests will appear as ERRORs.
Aborted
make[1]: *** [override_dh_auto_test] Error 134
make[1]: Leaving directory `/build/buildd/pyzmq-2.1.10'
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Tags: ftbfs precise
Revision history for this message
Julian Taylor (jtaylor) wrote :

something is broken on the i386/amd64 archive builders. The testsuite fails to bind to localhost.
see e.g. this message:
  File "/build/buildd/pyzmq-2.1.10/zmq/tests/test_context.py", line 166, in block
    s.bind_to_random_port('tcp://127.0.0.1')
  File "socket.pyx", line 519, in zmq.core.socket.Socket.bind_to_random_port (zmq/core/socket.c:5151)
ZMQBindError: Could not bind socket to random port.

it works fine on the arm/powerpc builders, locally and debians amd64/i386 builders.

Revision history for this message
Julian Taylor (jtaylor) wrote :

elmo on #launchpad found that zmq uses CLOEXEC which is not available on the i386 and amd64 kernels
requested upstream if the feature check can be made at runtime time instead of build time
https://zeromq.jira.com/browse/LIBZMQ-273

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package zeromq - 2.1.10-1ubuntu1

---------------
zeromq (2.1.10-1ubuntu1) precise; urgency=low

  * sock_cloexec-runtime-check.patch: (LP: #910757)
    check at runtime for SOCK_CLOEXEC support in kernel
    allows using testsuite on builders running 2.6.24
 -- Julian Taylor <email address hidden> Thu, 19 Jan 2012 18:43:25 +0100

Changed in zeromq (Ubuntu):
status: New → Fix Released
Revision history for this message
Julian Taylor (jtaylor) wrote :

pyzmq now builds
the testsuite still fails occasionally, but thats a different issue.

Changed in pyzmq (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Julian Taylor (jtaylor) wrote :

libzeromq-perl also built successfully now

Changed in libzeromq-perl (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.