1. 17 May, 2019 1 commit
  2. 18 Apr, 2019 1 commit
  3. 23 Mar, 2019 2 commits
  4. 22 Mar, 2019 1 commit
  5. 16 Mar, 2019 1 commit
  6. 07 Feb, 2019 3 commits
  7. 02 Feb, 2019 1 commit
  8. 13 Sep, 2018 1 commit
  9. 09 Sep, 2018 1 commit
    • Christoph Schulz's avatar
      Conform to `cmakelint --filter=-linelength` · a21228b6
      Christoph Schulz authored
      - Lowercase all commands
      - Unify indent to 2 spaces
      - Remove spaces around brackets
      - Remove repitition of condition in else(...) and endif(...)
      
      Note: (re-)running CMake did not change the content of the generated files
      a21228b6
  10. 23 Aug, 2018 1 commit
  11. 16 Aug, 2018 2 commits
  12. 15 Aug, 2018 1 commit
  13. 23 Jun, 2018 1 commit
  14. 01 Jun, 2018 1 commit
  15. 24 May, 2018 2 commits
  16. 23 May, 2018 2 commits
  17. 28 Apr, 2018 1 commit
  18. 16 Mar, 2018 2 commits
  19. 15 Mar, 2018 1 commit
  20. 14 Mar, 2018 2 commits
  21. 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
  22. 07 Mar, 2018 1 commit
  23. 02 Mar, 2018 1 commit
  24. 13 Feb, 2018 1 commit
  25. 11 Feb, 2018 1 commit
  26. 20 Nov, 2017 1 commit
  27. 19 Nov, 2017 1 commit
  28. 05 Oct, 2017 1 commit
  29. 19 Sep, 2017 1 commit
    • Luca Boccassi's avatar
      Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 · edb4ca10
      Luca Boccassi authored
      Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1,
      which means a reconnection will not be attempted, send a message from
      the I/O thread to the application thread to make the socket call
      term_endpoint, which is the equivalent of manually calling
      zmq_disconnect.
      This way subsequent zmq_connect call to the same endpoint will attempt
      again to do a connection.
      Otherwise, for some socket types like SUBs, those new connects will
      fail as the endpoint is recorded, despite the connection having been
      permanently closed.
      
      Add test cases to exercise this corner case with TCP and IPC.
      edb4ca10
  30. 01 Sep, 2017 1 commit
  31. 22 Aug, 2017 1 commit
  32. 21 Aug, 2017 1 commit