- 27 Mar, 2018 2 commits
-
-
Luca Boccassi authored
Solution: don't run configure
-
Min RK authored
* always run tests from tarball of `make dist` ensures that tests will not pass if critical files are omitted from releases * add explicit make dist only for non-default builds distcheck should already cover this for default builds * don’t verify that valgrind/coverage tests can be run from dists * add various files missing from dists - missing template from cmake - add missing android build files - add some missing ci_build.sh scripts
-
- 09 Mar, 2018 1 commit
-
-
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
-
- 12 Feb, 2018 1 commit
-
-
Luca Boccassi authored
* Problem: build failure with select as polling mechanism Solution: cast mailbox_handle argument to (poller_t::handle_t) like in the reaper thread class. * Problem: build failure due to INT_MAX use without include Solution: include limits and climits in src/select.cpp where INT_MAX is used * Problem: build failure due to unused variable in select.cpp Solution: move the declaration of int rc inside the ifdef block where it is actually used * Problem: reference to wrong variable in select.cpp breaks build Solution: fix it * Problem: family_entry_t constructor has no body, build fails on *nix Solution: add empty inline function in the struct * Problem: no test coverage for poll and select Solution: add Travis jobs for them on Linux * Problem: Travis jobs cannot run in container infra Solution: set sudo: false as it is not required anymore
-
- 17 Oct, 2017 1 commit
-
-
Luca Boccassi authored
Solution: install package and enable the build on some Linux jobs
-
- 19 Aug, 2017 2 commits
-
-
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
-
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
-
- 01 May, 2017 5 commits
-
-
Luca Boccassi authored
Solution: add Ubuntu toolchain PPA and use GCC 6
-
Luca Boccassi authored
Solution: pass -g so that valgrind/asan can print useful backtraces
-
Luca Boccassi authored
Solution: import better solution from zproject and add a new autoconf option
-
Luca Boccassi authored
Solution: run make with -j5, as now the tests support it.
-
Luca Boccassi authored
Solution: don't, libzmq's CI tests are not responsible for testing libsodium stable releases. Save some time in the CI.
-
- 30 Mar, 2017 1 commit
-
-
Luca Boccassi authored
Solution: add a CI build run with GCC's Address Sanitizer enabled. This compiler flag will make the unit test programs abort if it detects errors such as out-of-bound memory access or use-after-free.
-
- 27 Dec, 2016 2 commits
-
-
Luca Boccassi authored
Solution: rework the bash test to avoid build failures as intended and make it an easier one-liner
-
Luca Boccassi authored
Solution: use packages on Ubuntu and brews on OSX. The packages and the brews are always kept up to date, so it's no use to rebuild the libsodium stable branch manually everytime.
-
- 09 May, 2016 1 commit
-
-
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.
-
- 02 May, 2016 1 commit
-
-
Luca Boccassi authored
Solution: do default test with DRAFT APIs enabled
-
- 06 Mar, 2016 2 commits
-
-
Luca Boccassi authored
Solution: run make dist-check, which will run additional tests, including making sure that the library is installable and the distributable tarball is buildable, along with the usual make and make check.
-
Luca Boccassi authored
Solution: simply run make VERBOSE=1 check instead of manually checking for return value and cat'ing the log file. With VERBOSE, on error the log file will be automatically printed.
-
- 11 Feb, 2016 2 commits
-
-
Luca Boccassi authored
Solution: establish a matrix of CI options. On one axis we have the build system (autotools, cmake, android) and on the other axis we have the encryption options (tweetnacl, libsodium or none).
-
Luca Boccassi authored
Solution: build by default with tweetnacl, and add sub-build project to test libsodium
-
- 04 Feb, 2016 1 commit
-
-
Luca Boccassi authored
Solution: checkout stable branch instead. Several warnings are printed when building from the master branch, and developers recommend using the stable branch instead.
-
- 19 Dec, 2015 1 commit
-
-
Constantin Rack authored
Solution: add `--depth 1` parameter to `git clone` commands
-
- 25 Nov, 2015 1 commit
-
-
Constantin Rack authored
Currently, a test fails on Travis-CI but that can not be reproduced locally. Without the contents of the test-suite.log, this is difficult to analyze. Solution: print test-suite.log if "make check" fails This is based on the following answer on SO: http://stackoverflow.com/a/32597140
-
- 16 Aug, 2015 3 commits
-
-
Luca Boccassi authored
-
Luca Boccassi authored
-
Luca Boccassi authored
-
- 02 Aug, 2015 1 commit
-
-
Luca Boccassi authored
ldconfig is not available on OSX, so Travis CI build fails
-
- 03 Nov, 2014 1 commit
-
-
Joe McIlvain authored
Solution: Add qt-android build system and add to travis-ci
-