1. 20 Nov, 2017 1 commit
  2. 17 Oct, 2017 1 commit
  3. 19 Aug, 2017 2 commits
    • Luca Boccassi's avatar
      Problem: Travis does not test PGM · 68ba6d17
      Luca Boccassi authored
      Solution: enable option and install build-dependency for the jobs that
      already install packages only, to minimise marginal cost in term of
      runtime
      68ba6d17
    • Luca Boccassi's avatar
      Problem: Travis does not test GSSAPI · f979ed4f
      Luca Boccassi authored
      Solution: enable option and install build-dependency for the jobs that
      already install packages only, to minimise marginal cost in term of
      runtime
      f979ed4f
  4. 04 Aug, 2017 1 commit
  5. 03 Aug, 2017 4 commits
    • Luca Boccassi's avatar
      Problem: OSX builds are very slow · 5b91eb54
      Luca Boccassi authored
      Solution: avoid running brew update and brew install binutils unless
      it's for the android cross-compilation, where it's necessary for
      greadelf.
      5b91eb54
    • Luca Boccassi's avatar
      Problem: 2 OSX libsodium Travis runs · 0c5731ac
      Luca Boccassi authored
      Solution: remove the non-draft test run, as OSX is very slow and
      overcrowded on Travis
      0c5731ac
    • Luca Boccassi's avatar
      Problem: additional doc-build test on Travis · d96b0f42
      Luca Boccassi authored
      Solution: remove it, as it takes time and it's enough to test once
      d96b0f42
    • Simon Giesecke's avatar
      Replace console output by monitoring events for curve security issues (#2645) · 5d4e30eb
      Simon Giesecke authored
      * Fixing #2002 one way of doing it
      
       * Mechanisms can implement a new method `error_detail()`
       * This error detail have three values for the moment: no_detail
       (default), protocol, encryption.
          + generic enough to make sense for all mechanisms.
          - low granularity level on information.
      
      * Fixing #2002: implementation of the error details
      
      The ZMQ_EVENT_HANDSHAKE_FAILED event carries the error details
      as value.
      
      * Removed Microsoft extenstion for enum member access
      
      This was leading to compilation error under linux.
      
      * Adaptation of CURVE test cases
      
      * Monitoring event: changed API for detailed events
      
      Removed ZMQ_EVENT_HANDSHAKE_FAILED and replaced it by:
      - ZMQ_EVENT_HANDSHAKE_FAILED_NO_DETAIL,
      - ZMQ_EVENT_HANDSHAKE_FAILED_PROTOCOL,
      - ZMQ_EVENT_HANDSHAKE_FAILED_ENCRYPTION
      
      Adaptation of text case `security_curve`
      
      * Removed event value comparison
      
      This was introduced for the previous API model adaptation
      
      * Removed the prints in std output and added missing details
      
      `current_error_detail` was not set in every protocol error cases
      
      * Fixed initialization of current_error_detail
      
      * Fixed error in greeting test case
      
      The handshake failure due to mechanism mismatch in greeting is actually
      a protocol error. The error handling method consider it like so and
      send a protocol handshake failure monitoring event instead of no_detail.
      
      Fixed the test_security_curve expectation as well.
      
      * Upgraded tests of monitoring events
      
      The tests check the number of monitoring events received
      
      * Problem: does not build under Linux or without ZMQ_DRAFT_API
      
      Solution:
      - properly use ZMQ_DRAFT_API conditional compilation
      - use receive timeouts instead of Sleep
      
      * Problem: duplicate definition of variable 'timeout'
      
      Solution: merged definitions
      
      * Problem: inconsistent timing dependencies
      
      Solution: reduce timing dependency by using timeouts at more places
      
      * Problem: assertion failure under Linux due to unexpected monitor event
      
      Solution: output event type to aid debugging
      
      * Problem: erroneous assertion code
      
      * Problem: assertion failure with a garbage server key due to an extra third event
      
      Solution: changed assertion to expect three events (needs to be checked)
      
      * Problem: extra include directive to non-existent file
      
      Solution: removed include directive
      
      * Problem: assertion failure on appveyor for unknown reason
      
      Solution: improve debug output
      
      * Problem: no build with libsodium and draft api
      
      Solution: add build configurations with libsodium and draft api
      
      * Problem: assertion failure on CI
      
      Solution: change assertion to reflect actual behaviour on CI (at least temporarily)
      
      * Problem: error in condition in assertion code
      
      * Problem: assertion failure on CI
      
      Solution: generalize assertion to match behavior on CI
      
      * Problem: assertion failures on CI
      
      Solution: removed inconsistent assertion on no monitor events before flushing
      improved debuggability by converting function into macro
      
      * Problem: diverging test code for three analogous test cases with garbage key
      
      Solution: extract common code into function
      
      * Problem: does not build without ZMQ_BUILD_DRAFT_API
      
      Solution: introduce dummy variable
      
      * Attempt to remove workaround regarding ZMQ_EVENT_HANDSHAKE_FAILED_NO_DETAIL again
      
      * Problem: EAGAIN error after handshake complete if there is no more data in inbuffer
      
      Solution: Skip tcp_read attempt in that case
      
      * Problem: handshaking event emitted after handshaking failed
      
      Solution: use stream_engine_t::handshaking instead of mechanism_t::status() to determine whether still handshaking
      
      * Include error code in debug output
      
      * Improve debugging output: output flushed events
      
      * Split up ZMQ_EVENT_HANDSHAKE_FAILED_PROTOCOL into ZMQ_EVENT_HANDSHAKE_FAILED_ZMTP and ZMQ_EVENT_HANDSHAKE_FAILED_ZAP
      
      * Fixed compilation without ZMQ_BUILD_DRAFT_API
      
      * Renamed ZMQ_EVENT_HANDSHAKE_SUCCEED to ZMQ_EVENT_HANDSHAKE_SUCCEEDED for language consistency
      
      * Renamed ZMQ_EVENT_HANDSHAKE_SUCCEED to ZMQ_EVENT_HANDSHAKE_SUCCEEDED for language consistency
      
      * Renamed ZMQ_EVENT_HANDSHAKE_SUCCEED to ZMQ_EVENT_HANDSHAKE_SUCCEEDED for language consistency
      
      * Fixed assert_monitor_event (require event instead of allowing no event)
      Reverted erroneous change to handshaking condition
      Renamed test_wrong_key to test_garbage_key
      Generalized assumption in test_garbage_key to allow for ZMQ_EVENT_HANDSHAKE_FAILED_NO_DETAIL with error == EPIPE
      
      * Better isolate test cases from each other by providing a fresh context & server for each
      
      * Added diagnostic output
      
      * Changed assertion to reflect actual behavior on CI
      
      * Fixed formatting, observe maximum line length
      
      * Fixed formatting, observe maximum line length
      
      * Increase timeout to check if this fixes valgrind run
      
      * Close server with close_zero_linger
      
      * Increase timeout to check if this fixes valgrind run
      
      * Increase timeout to check if this fixes valgrind run
      
      * Generalize assertion to also work with valgrind
      
      * Fixed formatting
      
      * Add more diagnostic output
      
      * Generalize assertion to also work with valgrind
      5d4e30eb
  6. 01 May, 2017 1 commit
  7. 30 Apr, 2017 1 commit
    • Luca Boccassi's avatar
      Problem: no way to deploy releases to OBS · f126da8b
      Luca Boccassi authored
      Solution: add new tokens to .travis.yml and change ci_deploy.sh
      script to use Github APIs to create a temporary branch at the tag,
      and the OBS APIs to trigger a source service run in the stable and
      draft release projects:
      network:messaging:zeromq:release-stable
      network:messaging:zeromq:release-draft
      
      The branch hack is unfortunately necessary as it is not possible to
      modify OBS sources with the token APIs, and it is also not possible
      to automatically fetch the latest tag in the service files.
      The temporary branch is immediately deleted.
      f126da8b
  8. 30 Mar, 2017 1 commit
  9. 03 Mar, 2017 1 commit
  10. 27 Dec, 2016 4 commits
  11. 24 Jul, 2016 1 commit
  12. 09 May, 2016 1 commit
    • Kevin Sapper's avatar
      Problem: Deploying release artifacts is a manual process · b2255811
      Kevin Sapper authored
      Solution: Use travis to deploy these artifacts automatically.
      
      The deployment is triggered by tagging on the zeromq/libzmq repository.
      Of the many builds travis is checking only the default one with
      libsodium and drafts disabled is used for deployment.
      
      For now the results of `make distcheck` are deployed as well as their
      md5 and sha1 hash sums. Further changes may upload a generated
      Changelog as well.
      b2255811
  13. 02 May, 2016 1 commit
  14. 18 Apr, 2016 1 commit
  15. 19 Mar, 2016 2 commits
  16. 13 Mar, 2016 1 commit
  17. 12 Feb, 2016 1 commit
  18. 11 Feb, 2016 2 commits
  19. 08 Feb, 2016 2 commits
  20. 16 Dec, 2015 1 commit
  21. 17 Aug, 2015 1 commit
    • Luca Boccassi's avatar
      CI run on OSX needs binutils · 0c4032b5
      Luca Boccassi authored
      OSX does not ship with binutils, need to install it before the script
      run via brew in order to be able to use greadelf, needed by the
      qt-android CI script.
      0c4032b5
  22. 16 Aug, 2015 1 commit
  23. 02 Aug, 2015 2 commits
  24. 04 Nov, 2014 1 commit
  25. 03 Nov, 2014 1 commit
  26. 19 Oct, 2014 1 commit
  27. 12 Aug, 2014 2 commits
  28. 13 Oct, 2013 1 commit