StarMirror/toxcore
1
0
Fork 0
mirror of https://github.com/irungentoo/toxcore.git synced 2024-03-22 13:30:51 +08:00
Code Issues Projects Releases Wiki Activity
459f8f2013
toxcore/.travis.yml

51 lines
1.0 KiB
YAML
Raw Normal View History

Added support of Travis CI
2013-06-25 08:56:38 +08:00
language: c
compiler:
Make Travis use clang
2013-07-18 06:19:41 +08:00
- clang
Move toxcore travis build scripts out of .travis.yml. This is in preparation for having multiple types of build. One of the future builds will be a hstox build, another may be frama-c or some other static analyser. It makes sense to split these up into multiple builds, because each of them can take a while, and running them in parallel will speed things up. Also, the hstox test coverage should be reported separately from the toxcore auto_test coverage.
2016-07-13 20:12:11 +08:00
- gcc
env:
matrix:
Check code formatting on Travis. We run astyle on Travis and check if there is a diff. The build terminates if git finds a difference.
2016-08-09 20:46:41 +08:00
# - BUILD=hstox
Move toxcore travis build scripts out of .travis.yml. This is in preparation for having multiple types of build. One of the future builds will be a hstox build, another may be frama-c or some other static analyser. It makes sense to split these up into multiple builds, because each of them can take a while, and running them in parallel will speed things up. Also, the hstox test coverage should be reported separately from the toxcore auto_test coverage.
2016-07-13 20:12:11 +08:00
- BUILD=toxcore
Added support of Travis CI
2013-06-25 08:56:38 +08:00
Start recording test coverage and move to ubuntu precise. - We use coveralls.io to report on test coverage and avoid getting below a certain threshold. The threshold is currently 60%, but we will be increasing it when it stabilises. - We use gcc/clang -ftest-coverage and gcov to measure C test coverage. - We switched to container based Travis build infrastructure, which has the advantage of faster boot times[1] (1-6s vs. 20-52s). The trusty beta supports caching, but the longer boot times make it an unattractive target. - We now need to build more dependencies ourselves and cache the result. We still fetch what we can (currently opam, libvpx, and check) from apt. [1] https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
2016-07-06 16:47:13 +08:00
addons:
apt:
sources:
- avsm
Run hstox test suite against toxcore on Travis.
2016-07-13 21:18:03 +08:00
- hvr-ghc
Start recording test coverage and move to ubuntu precise. - We use coveralls.io to report on test coverage and avoid getting below a certain threshold. The threshold is currently 60%, but we will be increasing it when it stabilises. - We use gcc/clang -ftest-coverage and gcov to measure C test coverage. - We switched to container based Travis build infrastructure, which has the advantage of faster boot times[1] (1-6s vs. 20-52s). The trusty beta supports caching, but the longer boot times make it an unattractive target. - We now need to build more dependencies ourselves and cache the result. We still fetch what we can (currently opam, libvpx, and check) from apt. [1] https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
2016-07-06 16:47:13 +08:00
packages:
Run hstox test suite against toxcore on Travis.
2016-07-13 21:18:03 +08:00
- cabal-install-1.22
Start recording test coverage and move to ubuntu precise. - We use coveralls.io to report on test coverage and avoid getting below a certain threshold. The threshold is currently 60%, but we will be increasing it when it stabilises. - We use gcc/clang -ftest-coverage and gcov to measure C test coverage. - We switched to container based Travis build infrastructure, which has the advantage of faster boot times[1] (1-6s vs. 20-52s). The trusty beta supports caching, but the longer boot times make it an unattractive target. - We now need to build more dependencies ourselves and cache the result. We still fetch what we can (currently opam, libvpx, and check) from apt. [1] https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
2016-07-06 16:47:13 +08:00
- check
Run hstox test suite against toxcore on Travis.
2016-07-13 21:18:03 +08:00
- ghc-7.10.3
Start recording test coverage and move to ubuntu precise. - We use coveralls.io to report on test coverage and avoid getting below a certain threshold. The threshold is currently 60%, but we will be increasing it when it stabilises. - We use gcc/clang -ftest-coverage and gcov to measure C test coverage. - We switched to container based Travis build infrastructure, which has the advantage of faster boot times[1] (1-6s vs. 20-52s). The trusty beta supports caching, but the longer boot times make it an unattractive target. - We now need to build more dependencies ourselves and cache the result. We still fetch what we can (currently opam, libvpx, and check) from apt. [1] https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
2016-07-06 16:47:13 +08:00
- libvpx-dev
Move toxcore travis build scripts out of .travis.yml. This is in preparation for having multiple types of build. One of the future builds will be a hstox build, another may be frama-c or some other static analyser. It makes sense to split these up into multiple builds, because each of them can take a while, and running them in parallel will speed things up. Also, the hstox test coverage should be reported separately from the toxcore auto_test coverage.
2016-07-13 20:12:11 +08:00
- opam # For apidsl and Frama-C.
- texinfo # For libconfig.
Start recording test coverage and move to ubuntu precise. - We use coveralls.io to report on test coverage and avoid getting below a certain threshold. The threshold is currently 60%, but we will be increasing it when it stabilises. - We use gcc/clang -ftest-coverage and gcov to measure C test coverage. - We switched to container based Travis build infrastructure, which has the advantage of faster boot times[1] (1-6s vs. 20-52s). The trusty beta supports caching, but the longer boot times make it an unattractive target. - We now need to build more dependencies ourselves and cache the result. We still fetch what we can (currently opam, libvpx, and check) from apt. [1] https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
2016-07-06 16:47:13 +08:00
cache:
directories:
Run hstox test suite against toxcore on Travis.
2016-07-13 21:18:03 +08:00
- $HOME/.cabal
- $HOME/.ghc
Start recording test coverage and move to ubuntu precise. - We use coveralls.io to report on test coverage and avoid getting below a certain threshold. The threshold is currently 60%, but we will be increasing it when it stabilises. - We use gcc/clang -ftest-coverage and gcov to measure C test coverage. - We switched to container based Travis build infrastructure, which has the advantage of faster boot times[1] (1-6s vs. 20-52s). The trusty beta supports caching, but the longer boot times make it an unattractive target. - We now need to build more dependencies ourselves and cache the result. We still fetch what we can (currently opam, libvpx, and check) from apt. [1] https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
2016-07-06 16:47:13 +08:00
- $HOME/cache
Move toxcore travis build scripts out of .travis.yml. This is in preparation for having multiple types of build. One of the future builds will be a hstox build, another may be frama-c or some other static analyser. It makes sense to split these up into multiple builds, because each of them can take a while, and running them in parallel will speed things up. Also, the hstox test coverage should be reported separately from the toxcore auto_test coverage.
2016-07-13 20:12:11 +08:00
install:
Run hstox test suite against toxcore on Travis.
2016-07-13 21:18:03 +08:00
# Set up PATH for the /opt packages.
- export PATH=/opt/cabal/1.22/bin:$PATH
- export PATH=/opt/ghc/7.10.3/bin:$PATH
Move toxcore travis build scripts out of .travis.yml. This is in preparation for having multiple types of build. One of the future builds will be a hstox build, another may be frama-c or some other static analyser. It makes sense to split these up into multiple builds, because each of them can take a while, and running them in parallel will speed things up. Also, the hstox test coverage should be reported separately from the toxcore auto_test coverage.
2016-07-13 20:12:11 +08:00
# Globally used environment variables.
- export CACHE_DIR=$HOME/cache
Start recording test coverage and move to ubuntu precise. - We use coveralls.io to report on test coverage and avoid getting below a certain threshold. The threshold is currently 60%, but we will be increasing it when it stabilises. - We use gcc/clang -ftest-coverage and gcov to measure C test coverage. - We switched to container based Travis build infrastructure, which has the advantage of faster boot times[1] (1-6s vs. 20-52s). The trusty beta supports caching, but the longer boot times make it an unattractive target. - We now need to build more dependencies ourselves and cache the result. We still fetch what we can (currently opam, libvpx, and check) from apt. [1] https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
2016-07-06 16:47:13 +08:00
- export OPAMROOT=$CACHE_DIR/.opam
Run hstox test suite against toxcore on Travis.
2016-07-13 21:18:03 +08:00
- export LD_LIBRARY_PATH=$CACHE_DIR/lib
Start recording test coverage and move to ubuntu precise. - We use coveralls.io to report on test coverage and avoid getting below a certain threshold. The threshold is currently 60%, but we will be increasing it when it stabilises. - We use gcc/clang -ftest-coverage and gcov to measure C test coverage. - We switched to container based Travis build infrastructure, which has the advantage of faster boot times[1] (1-6s vs. 20-52s). The trusty beta supports caching, but the longer boot times make it an unattractive target. - We now need to build more dependencies ourselves and cache the result. We still fetch what we can (currently opam, libvpx, and check) from apt. [1] https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
2016-07-06 16:47:13 +08:00
- export PKG_CONFIG_PATH=$CACHE_DIR/lib/pkgconfig
Move toxcore travis build scripts out of .travis.yml. This is in preparation for having multiple types of build. One of the future builds will be a hstox build, another may be frama-c or some other static analyser. It makes sense to split these up into multiple builds, because each of them can take a while, and running them in parallel will speed things up. Also, the hstox test coverage should be reported separately from the toxcore auto_test coverage.
2016-07-13 20:12:11 +08:00
- export ASTYLE=$CACHE_DIR/astyle/build/gcc/bin/astyle
# Install required packages.
- other/travis/${BUILD}-install
First part of DHT hardening done. Added crypto to the DHT communications. This defeats completely the first attack mentioned in docs/DHT_hardening. Also updated the build system to build the latest test (it links it with libsodium)
2013-07-13 04:27:19 +08:00
Added support of Travis CI
2013-06-25 08:56:38 +08:00
script:
Move toxcore travis build scripts out of .travis.yml. This is in preparation for having multiple types of build. One of the future builds will be a hstox build, another may be frama-c or some other static analyser. It makes sense to split these up into multiple builds, because each of them can take a while, and running them in parallel will speed things up. Also, the hstox test coverage should be reported separately from the toxcore auto_test coverage.
2016-07-13 20:12:11 +08:00
- other/travis/${BUILD}-script
Added support of Travis CI
2013-06-25 08:56:38 +08:00
Start recording test coverage and move to ubuntu precise. - We use coveralls.io to report on test coverage and avoid getting below a certain threshold. The threshold is currently 60%, but we will be increasing it when it stabilises. - We use gcc/clang -ftest-coverage and gcov to measure C test coverage. - We switched to container based Travis build infrastructure, which has the advantage of faster boot times[1] (1-6s vs. 20-52s). The trusty beta supports caching, but the longer boot times make it an unattractive target. - We now need to build more dependencies ourselves and cache the result. We still fetch what we can (currently opam, libvpx, and check) from apt. [1] https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
2016-07-06 16:47:13 +08:00
after_script:
Move toxcore travis build scripts out of .travis.yml. This is in preparation for having multiple types of build. One of the future builds will be a hstox build, another may be frama-c or some other static analyser. It makes sense to split these up into multiple builds, because each of them can take a while, and running them in parallel will speed things up. Also, the hstox test coverage should be reported separately from the toxcore auto_test coverage.
2016-07-13 20:12:11 +08:00
- other/travis/${BUILD}-after_script
Fixed cmake and Travis
2013-07-13 06:31:57 +08:00
Fix a few issues with running Toxcore tests on Travis-CI > increased the timeout for TCP tests because per @irungentoo the network on Travis-CI can be slow sometimes > allowed groupchats test to restart on error until timeout This had to be done because current groupchats are fundamentally broken and 3/5 times they'll 'net-split' on connect >> Drop group chat tests, add comment to the reason > added some debugging information to TCP tests, and a #define to force IPV6 (Travis-CI only uses IPv4 on their containers) and decreased the itr interval > Went crazy with timeouts for Tox network stuff on Travis. Tests on TCP will still randomly fail due to timeouts. I can't reproduce on any local system. So again per @irungentoo, Travis is slow, let's offer it a short bus.
2016-07-13 03:32:35 +08:00
notifications:
irc: "chat.freenode.net#toktok-status"
Reference in New Issue Copy Permalink