1. 09 Mar, 2018 1 commit
    • Luca Boccassi's avatar
      Problem: TIPC availability check is too strict (#2977) · 19060345
      Luca Boccassi authored
      * Problem: TIPC availability check is too strict
      
      Solution: at build time only check if the API is available. In the tests
      do a first check and a skip if the functionality is not available.
      
      TIPC needs an in-tree but not loaded by default kernel module, tipc.ko
      to be loaded, which requires root, so it is unlikely to be available on
      any build system by default.
      This will allow most distributions to ship with TIPC support built in,
      and to avoid tests failure if the module is not there.
      
      * Problem: no Travis tests for TIPC
      
      Solution: mark one job with sudo: required and load the kernel module
      
      * Problem: CMake fails when test returns 77 (skip)
      
      Solution: set property to let it mark the test as skipped as intended
      19060345
  2. 02 Feb, 2018 1 commit
  3. 11 May, 2016 1 commit
    • Erik Hugne's avatar
      tipc: add support for address domain suffix · f81ef1bc
      Erik Hugne authored
      The TIPC protocol bindings in ZeroMQ defaults to a lookup domain
      of 1.0.0 to prevent 'closest first' search, and instead always
      do round robin if several sockets in the network or node have
      the same name published. In retrospect, this might have been a
      bad idea because it won't work on standalone configurations.
      We solve this by allowing an optional domain suffix to be provided
      in the address, and 0.0.0 should be used in that case, or if the
      TIPC address range in the cluster configuration is defined to some
      other value. Domain suffixes are only relevant for connecting
      addresses.
      Signed-off-by: 's avatarErik Hugne <erik.hugne@gmail.com>
      f81ef1bc
  4. 12 Feb, 2016 1 commit
    • Pieter Hintjens's avatar
      Problem: tests don't build on Windows · bbcc79d1
      Pieter Hintjens authored
      There were numerous small issues with test cases:
      
      - some lacked the right source file header
      - some were not portable at all
      - some were using internal libzmq APIs (headers)
      
      Solution: fixed and cleaned up.
      bbcc79d1
  5. 01 Feb, 2016 3 commits
  6. 02 Jun, 2015 1 commit
  7. 01 Nov, 2013 1 commit
  8. 15 Sep, 2013 1 commit
    • Pieter Hintjens's avatar
      Added z85 codec to ZMQ API · 576e3ca5
      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
      576e3ca5
  9. 17 Aug, 2013 1 commit
  10. 12 Mar, 2013 1 commit
  11. 31 Jan, 2013 2 commits
  12. 06 Sep, 2012 1 commit
    • Arthur O'Dwyer's avatar
      Add "#undef NDEBUG" to all tests. · cf20932d
      Arthur O'Dwyer authored
      This change makes sure that even if the tests are built in a
      "release" configuration (with optimizations and NDEBUG turned on),
      the assertions won't get compiled out of the tests themselves.
      
      The C standard guarantees that the most recent inclusion of
      <assert.h> is the one that counts, so it's important that the
      "#undef NDEBUG/#include <assert.h>" come as the last thing in
      the block of header files.
      
      "testutil.hpp" includes <assert.h>, so I've left <assert.h> out
      of any test that #includes "testutil.hpp", just for the sake of
      brevity.
      cf20932d
  13. 27 Aug, 2012 1 commit
  14. 01 Nov, 2011 2 commits
  15. 31 Oct, 2011 1 commit
  16. 24 Mar, 2011 1 commit
  17. 02 Mar, 2011 1 commit
  18. 30 Oct, 2010 1 commit
  19. 28 Aug, 2010 1 commit
  20. 27 Aug, 2010 2 commits
  21. 13 Feb, 2010 1 commit
  22. 05 Jan, 2010 1 commit
  23. 10 Dec, 2009 1 commit
  24. 03 Nov, 2009 1 commit
  25. 05 Oct, 2009 1 commit
  26. 03 Aug, 2009 1 commit
  27. 29 Jul, 2009 1 commit