You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that version 4 of ØMQ changed its semantics to allow the case that the first test in 100_basic.t expects to fail. The result is, as far as I understand it, that the test unexpectedly succeeds and when perl tries to GC the client socket ØMQ refuses to destroy it until it's completed it's initialization. Since that never happens, the effect is to make the test hang. Adding an "else" branch that does zmq_bind() makes the test proceed (and report failure).
I don't know if this test still tests something interesting on ØMQ 4, or should just be skipped in that case.
All other tests pass with ØMQ 4.0.3
The text was updated successfully, but these errors were encountered:
I don't plan on working with ZMQ (and even less with ZMQ4) in the near future, and so I'm not going to spend time debugging this code. I'm willing to review code and do release management if necessary, but please send me pull reqs if this needs to be resolved.
It appears that version 4 of ØMQ changed its semantics to allow the case that the first test in 100_basic.t expects to fail. The result is, as far as I understand it, that the test unexpectedly succeeds and when perl tries to GC the client socket ØMQ refuses to destroy it until it's completed it's initialization. Since that never happens, the effect is to make the test hang. Adding an "else" branch that does zmq_bind() makes the test proceed (and report failure).
I don't know if this test still tests something interesting on ØMQ 4, or should just be skipped in that case.
All other tests pass with ØMQ 4.0.3
The text was updated successfully, but these errors were encountered: