- 14 Sep, 2015 1 commit
-
-
Richard Newton authored
-
- 11 Sep, 2015 1 commit
-
-
Pieter Hintjens authored
This is due to the mangled include of platform.h, which was to make CMake happy. Solution: in CMakeLists.txt, define USING_CMAKE and then look for platform.h in current directory if that is defined, else look in ../src/ as one would expect.
-
- 11 Aug, 2015 2 commits
-
-
Pieter Hintjens authored
-
Pieter Hintjens authored
Solution: added to test_stream.cpp
-
- 28 Jul, 2015 1 commit
-
-
Brian Silverman authored
It's nice to be able to disable libzmq's internal timeout when there's another timeout in the test runner being used which gives nicer error messages.
-
- 02 Jun, 2015 1 commit
-
-
Pieter Hintjens authored
Of course people still "can" distributed the sources under the LGPLv3. However we provide COPYING.LESSER with additional grants. Solution: specify these grants in the header of each source file.
-
- 30 Jan, 2015 1 commit
-
-
Pieter Hintjens authored
Solution: raise timeouts from 100-150 msec to 250 msec
-
- 26 Jan, 2015 1 commit
-
-
Richard Newton authored
-
- 23 Jan, 2015 1 commit
-
-
Pieter Hintjens authored
Symptom is that ZMQ_STREAM sockets in 4.1.0 and 4.1.1 generate zero sized messages on each new connection, unlike 4.0.x which did not do this. Person who made this commit also changed test cases so that contract breakage did not show. Same person was later banned for persistently poor form in CZMQ contributions. Solution: enable connect notifications on ZMQ_STREAM sockets using a new ZMQ_STREAM_NOTIFY setting. By default, socket does not deliver notifications, and behaves as in 4.0.x. Fixes #1316
-
- 22 Jan, 2015 1 commit
-
-
Pieter Hintjens authored
Solution: update for 2015 Fixes #1320
-
- 29 Dec, 2014 1 commit
-
-
DaiyuHurst authored
-
- 23 Dec, 2014 1 commit
-
-
Pieter Hintjens authored
Solution: increase settle time for bind/unbind tests
-
- 23 Jul, 2014 1 commit
-
-
Ewen McNeill authored
Updated: tests/testutil.hpp: Add signal(SIGPIPE, SIG_IGN) to setup_test_environment(), on z/OS (__MVS__)
-
- 27 Jun, 2014 1 commit
-
-
Pieter Hintjens authored
Users who need e.g. zmq_curve_keypair() have to remember to include zmq_utils.h, which is counter-intuitive. The whole library should be represented by a single include file. Solution: merge all contents of zmq_utils.h into zmq.h, and deprecate zmq_utils.h. Existing apps can continue unchanged. New apps can ignore zmq_utils.h completely.
-
- 20 May, 2014 1 commit
-
-
Pieter Hintjens authored
The expect_bounce_fail () helper assumed that messages could always be sent. However in some cases zmq_send() blocks, due to there not being any outgoing pipe. This changed in 77f5f7, where previously there would be a pipe that kept trying to reconnect forever. Solution: use a send timeout and check for EAGAIN if sending failed.
-
- 19 May, 2014 2 commits
-
-
Goswin von Brederlow authored
will not block too long if they go wrong.
-
Goswin von Brederlow authored
failures don't block.
-
- 02 May, 2014 2 commits
-
-
Pieter Hintjens authored
This reverts commit 2a84d259. Broke regression test on test_hwm.cpp.
-
dave b authored
These changes cause an assertion in lb_sendpipe() when executing the test_security_plain testcase.
-
- 28 Apr, 2014 1 commit
-
-
Pieter Hintjens authored
Specifically: * zmq_event_t should not be used internally in libzmq, it was meant to be an outward facing structure. * In 4.x, zmq_event_t does not correspond to monitor events, so I removed the structure entirely. * man page for zmq_socket_monitor is incomplete and the example code was particularly nasty. * test_monitor.cpp needed rewriting, it was not clean.
-
- 20 Jan, 2014 1 commit
-
-
Ivan Pechorin authored
-
- 02 Jan, 2014 1 commit
-
-
Pieter Hintjens authored
-
- 19 Nov, 2013 2 commits
-
-
Pieter Hintjens authored
-
Pieter Hintjens authored
* failed on systems where process could not allocate 1024 sockets by default * include path for platform.hpp was wrong; fixed it
-
- 06 Nov, 2013 1 commit
-
-
Pieter Hintjens authored
- used msleep (10) in most places instead of zmq_sleep (1) - may cause failures on slower machines - to change, modify SETTLE_TIME in testutil.h - tested down to 1 msec on fast boxes
-
- 18 Oct, 2013 1 commit
-
-
Laurent Alebarde authored
-
- 04 Oct, 2013 1 commit
-
-
KIU Shueng Chuan authored
-
- 20 Sep, 2013 2 commits
-
-
AJ Lewis authored
- 16 Sep, 2013 1 commit
-
-
Richard Newton authored
-
- 15 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
* Removed redundant Z85 code and include files from project * Simplified use of headers in test cases (now they all just use testutil.hpp) * Export zmq_z85_encode() and zmq_z85_decode() in API * Added man pages for these two functions
-
- 12 Sep, 2013 1 commit
-
-
Laurent Alebarde authored
-
- 02 Sep, 2013 2 commits
-
-
Pieter Hintjens authored
- if ZAP server returns anything except 200, connection is closed - all security tests now pass correctly - test_security_curve now does proper client key authentication using test key - test_security_plain now does proper password authentication
-
Pieter Hintjens authored
- Split off NULL security check from PLAIN - Cleaned up test_linger code a little - Got all tests to pass, added TODOs for outstanding issues - Added ZAP authentication for NULL test case - NULL mechanism was not passing server identity - fixed - cleaned up test_security_plain and removed option double-checks (made code ugly) - lowered timeout on expect_bounce_fail to 150 msec to speed up checks - removed all sleeps from test_fork and simplified code (it still passes :-)
-
- 31 Aug, 2013 1 commit
-
-
MinRK authored
adds expect_bounce_fail test function which is like bounce, but fails if messages arrive.
-
- 17 Aug, 2013 2 commits
-
-
Richard Newton authored
-
Richard Newton authored
-
- 07 Jul, 2013 1 commit
-
-
Pieter Hintjens authored
* disabled the specific tests that do not work (yet) on libzmq * cleaned up one source (test_spec_rep.c) but the others need similar work * added sleep in test_spec_rep to allow connects time to happen; this would not be needed if we connected out to the REP peers instead in from them, but I didn't want to change the logic of the test code.
-
- 05 Jul, 2013 1 commit
-
-
Christian Kamm authored
The inproc:// endpoints sometimes use different code paths so testing with regular tcp:// endpoints as well can show different issues.
-
- 02 Jul, 2013 1 commit
-
-
Christian Kamm authored
* See http://rfc.zeromq.org/spec:28/REQREP * Not all testable statements are covered. * At this point, there are several failures: - test_spec_req: The REQ socket does not correctly discard messages from peers that are not currently being talked to. - test_spec_dealer/router: On disconnect, the queues seem to not be emptied. The DEALER can still receive a message the disconnected peer sent, the ROUTER can still send to the identity of the dis- connected peer.
-