1. 01 May, 2017 1 commit
    • Luca Boccassi's avatar
      Problem: tests bind to hardcoded TCP ports · 5934919f
      Luca Boccassi authored
      Solution: use ZMQ_LAST_ENDPOINT in most places. This alllows running
      tests in paralle, and on over-booked shared machines where many of
      the ports would be already in use.
      Keep 3 tests with an hardcoded port, as there are some code paths that
      require it (eg: connect before bind), but list those ports in
      tests/testutil.hpp as macros so that they do not overlap and still
      allow parallel runs.
      
      These changes were inspired by a patch uploaded to Ubuntu by the
      package maintainer, Steve Langasek <steve.langasek@ubuntu.com>.
      Thank you Steve!
      5934919f
  2. 06 Dec, 2016 1 commit
  3. 27 Aug, 2016 1 commit
  4. 23 Aug, 2016 2 commits
  5. 12 Jul, 2016 1 commit
  6. 02 May, 2016 1 commit
  7. 18 Apr, 2016 1 commit
    • Luca Boccassi's avatar
      Problem: can't test if IPv6 is available in tests · ac0e97e5
      Luca Boccassi authored
      Solution: add helper function is_ipv6_available to testutil.hpp to
      test if IPv6 is available on the building platform.
      This function will try to open and bind a socket to ::1:*, as it's
      the ultimate way of knowing if, at least on the loopback, IPv6 is
      enabled.
      ac0e97e5
  8. 13 Feb, 2016 2 commits
  9. 12 Feb, 2016 1 commit
    • Pieter Hintjens's avatar
      Problem: gyp does not build tests · 8230c0d3
      Pieter Hintjens authored
      Solution: it's a lot of work to define the tests in project.gyp
      so I did this using gsl to generate the JSON, from a small XML
      list of the test cases.
      
      To keep this, and the hundreds of .mk files, away from the root
      directory, I've moved the gyp files into builds/gyp, where you
      would run them.
      
      It all seems to work now. Next up, OS/X and Windows :)
      8230c0d3
  10. 28 Jan, 2016 1 commit
  11. 14 Sep, 2015 1 commit
  12. 11 Sep, 2015 1 commit
    • Pieter Hintjens's avatar
      Problem: cannot build single test case in tests · d416ffce
      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.
      d416ffce
  13. 11 Aug, 2015 2 commits
  14. 28 Jul, 2015 1 commit
  15. 02 Jun, 2015 1 commit
  16. 30 Jan, 2015 1 commit
  17. 26 Jan, 2015 1 commit
  18. 23 Jan, 2015 1 commit
    • Pieter Hintjens's avatar
      Problem: commit afb24b53 broke ZMQ_STREAM contract · 6ced7027
      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
      6ced7027
  19. 22 Jan, 2015 1 commit
  20. 29 Dec, 2014 1 commit
  21. 23 Dec, 2014 1 commit
  22. 23 Jul, 2014 1 commit
  23. 27 Jun, 2014 1 commit
    • Pieter Hintjens's avatar
      Problem: two header files for a single library · a087ce55
      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.
      a087ce55
  24. 20 May, 2014 1 commit
    • Pieter Hintjens's avatar
      Problem: security tests block on zmq_send · 11175a33
      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.
      11175a33
  25. 19 May, 2014 2 commits
  26. 02 May, 2014 2 commits
  27. 28 Apr, 2014 1 commit
    • Pieter Hintjens's avatar
      Problem: zmq_socket_monitor code is dirty · 9753de85
      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.
      9753de85
  28. 20 Jan, 2014 1 commit
  29. 02 Jan, 2014 1 commit
  30. 19 Nov, 2013 2 commits
  31. 06 Nov, 2013 1 commit
    • Pieter Hintjens's avatar
      Removed over-long pauses in tests · 5b60540e
      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
      5b60540e
  32. 18 Oct, 2013 1 commit
  33. 04 Oct, 2013 1 commit
  34. 20 Sep, 2013 1 commit