1. 09 May, 2019 1 commit
  2. 02 May, 2019 2 commits
  3. 24 Mar, 2019 1 commit
  4. 23 Mar, 2019 1 commit
  5. 27 May, 2018 1 commit
  6. 14 May, 2018 3 commits
  7. 16 Mar, 2018 1 commit
  8. 15 Mar, 2018 4 commits
  9. 02 Feb, 2018 1 commit
  10. 01 Sep, 2017 1 commit
  11. 22 Aug, 2017 9 commits
  12. 18 May, 2017 1 commit
  13. 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
  14. 12 May, 2016 1 commit
    • hitstergtd's avatar
      Problem: zmq_poller_destroy parameter checking · 477cc1cb
      hitstergtd authored
      Solution:
      - Add checks for **poller_p_ to ensure that we do not segfault when either it
        or the value within it are NULL
      - Add tests for the above and increase error state coverage
      477cc1cb
  15. 05 May, 2016 1 commit
  16. 02 May, 2016 1 commit
  17. 12 Apr, 2016 1 commit
    • Patrik Wenger's avatar
      Problem: tricky return value from zmq::socket_poller_t::wait when poller is empty · 621c965f
      Patrik Wenger authored
      Solution: return -1 (no event) instead of 0 (event)
      
      For some reason, this just returns 0 if there are no sockets registered
      on the poller. Usually this would mean there has been an event. So the
      caller would have to check the return value AND the event, or write code
      that takes the number of registered sockets into consideration.
      
      By returning -1 and setting errno = ETIMEDOUT like in the usual timeout
      cases, it's more consistent and convenient.
      
      Test case included.
      621c965f
  18. 01 Feb, 2016 1 commit
  19. 28 Jan, 2016 1 commit
  20. 21 Dec, 2015 1 commit
  21. 22 Oct, 2015 1 commit
  22. 21 Oct, 2015 2 commits
  23. 18 Oct, 2015 1 commit
  24. 17 Aug, 2015 2 commits