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
ba95314845
toxcore/.travis.yml

88 lines
2.6 KiB
YAML
Raw Normal View History

Enable .travis.yml check and use non-markdown license.
2018-08-18 07:48:33 +08:00
---
Run fewer Travis jobs during Pull Requests. Still run all the jobs during cron and regular push to branch. We disabled build for push to branch, so cron is the only place where all builds are run. This also means we need to worry less about spending time in nightly builds, because they occur only once a day. See https://github.com/travis-ci/travis-ci/issues/9071
2018-01-16 04:24:44 +08:00
# For Pull Requests, we build only the first three jobs: autotools on Linux,
# cmake on Linux, and cmake on Windows 32 bit.
#
Use ninja build system for the cmake-linux build.
2020-03-03 06:13:31 +08:00
# For branch builds and cron builds (once a day), we build all the jobs. This is
# achieved using the "if: type IN (push, api, cron)" fields in the jobs list.
Run fewer Travis jobs during Pull Requests. Still run all the jobs during cron and regular push to branch. We disabled build for push to branch, so cron is the only place where all builds are run. This also means we need to worry less about spending time in nightly builds, because they occur only once a day. See https://github.com/travis-ci/travis-ci/issues/9071
2018-01-16 04:24:44 +08:00
Added support of Travis CI
2013-06-25 08:56:38 +08:00
language: c
Add a mutex lock/unlock inside every public API function.
2020-03-06 20:10:47 +08:00
dist: xenial
Use ninja build system for the cmake-linux build.
2020-03-03 06:13:31 +08:00
os: linux
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
Use ninja build system for the cmake-linux build.
2020-03-03 06:13:31 +08:00
jobs:
Add and use CMake build script Also, fix the hstox build that was taking half an hour. It now takes 5 minutes. Also, perform distcheck on travis to ensure that make dist works. It's not actually failing the build at the moment due to broken tests.
2016-08-10 19:28:33 +08:00
include:
Enable .travis.yml check and use non-markdown license.
2018-08-18 07:48:33 +08:00
- stage: "Stage 1"
env: JOB=cmake-linux
compiler: gcc
addons:
apt:
packages:
- libconfig-dev # For tox-bootstrapd.
- libopus-dev # For toxav.
- libgtest-dev # For unit tests.
- libvpx-dev # For toxav.
Use ninja build system for the cmake-linux build.
2020-03-03 06:13:31 +08:00
- ninja-build
Add tool to find directly recursive calls in toxcore. We should avoid recursion, as it makes reasoning about stack growth harder. This tool shows (currently) 4 (non-tail) recursive functions, at least 2 of which are easy to fix.
2018-08-27 23:51:41 +08:00
- pylint
Enable .travis.yml check and use non-markdown license.
2018-08-18 07:48:33 +08:00
install: .travis/$JOB install
script: .travis/$JOB script
after_script: .travis/upload-coverage
- stage: "Stage 1"
env: JOB=autotools-linux
compiler: clang
addons:
apt:
packages:
- libconfig-dev # For tox-bootstrapd.
- libopus-dev # For toxav.
- libvpx-dev # For toxav.
install: .travis/$JOB install
script: .travis/$JOB script
- stage: "Stage 1"
if: type IN (push, api, cron)
env: JOB=cmake-win32
services: [docker]
install: .travis/$JOB install
script: .travis/$JOB script
- stage: "Stage 1"
if: type IN (push, api, cron)
env: JOB=cmake-win64
services: [docker]
install: .travis/$JOB install
script: .travis/$JOB script
Enable FreeBSD jobs on Travis-CI
2020-03-10 18:35:48 +08:00
- stage: "Stage 1"
if: type IN (push, api, cron)
env: JOB=cmake-freebsd
install: .travis/$JOB-stage1 install
script: .travis/$JOB-stage1 script
Enable .travis.yml check and use non-markdown license.
2018-08-18 07:48:33 +08:00
- stage: "Stage 1"
if: type IN (push, api, cron)
env: JOB=cmake-osx
os: osx
install: .travis/$JOB install
script: .travis/$JOB script
- stage: "Stage 1"
if: type IN (push, api, cron)
env: JOB=tox-bootstrapd-docker
services: [docker]
script: .travis/$JOB
Enable FreeBSD jobs on Travis-CI
2020-03-10 18:35:48 +08:00
- stage: "Stage 2"
if: type IN (push, api, cron)
env: JOB=cmake-freebsd
install: .travis/$JOB-stage2 install
script: .travis/$JOB-stage2 script
Allow the OSX build to fail on travis. Given that it fails about 80-90% of the time, it's not worth requiring it to pass. Instead, we'll need to manually look at the osx build to see in what way it failed. Also, set `fast_finish` to true, since OSX regularly has multi-hour (up to half a day) outages that can't block us for trivial code changes or non-code changes.
2016-09-22 21:42:29 +08:00
fast_finish: true
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
cache:
directories:
Enable .travis.yml check and use non-markdown license.
2018-08-18 07:48:33 +08:00
- $HOME/.cache/bazel
- $HOME/cache
- /opt/freebsd/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
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:
TravisCI shorten IRC message
2016-10-31 02:29:14 +08:00
irc:
channels:
Enable .travis.yml check and use non-markdown license.
2018-08-18 07:48:33 +08:00
- "chat.freenode.net#toktok-status"
TravisCI shorten IRC message
2016-10-31 02:29:14 +08:00
template:
Enable .travis.yml check and use non-markdown license.
2018-08-18 07:48:33 +08:00
- "%{result} %{repository_name} %{build_url}"
- "#%{build_number} changes: %{compare_url}"
Reference in New Issue Copy Permalink