kevin/neovim
1
Fork 0
mirror of https://github.com/neovim/neovim.git synced 2024-12-19 18:55:14 -07:00
Code Issues Packages Projects Releases Wiki Activity
58b210e114
neovim/.travis.yml

130 lines
3.8 KiB
YAML
Raw Normal View History

ci: Upgrade to ubuntu 14.04 "trusty"
2016-12-26 11:23:54 -07:00
dist: trusty
Travis: Refactor CI files, use container infrastructure. * Split build steps to utilize the Travis build lifecycle. * Move shell code from `.travis.yml` into Bash files in `.ci/`, one file for each step of the Travis build lifecycle. * Use configuration variables in `.travis.yml` to change build behavior (e.g. build 32-bit with `BUILD_32BIT=ON`). * Keep all configuration in environment variables in `.travis.yml`. In scripts, concatenate environment variables according to configuration to change to different behavior. * Add GCC 5 builds for Linux. * Use Travis's caching feature [1] for third-party dependencies and pip packages. * Allow failures MSan, as the errors it reports have to be fixed first. Valgrind is still disabled, but can be enabled by setting `env: VALGRIND=ON` for a job in `.travis.yml`. [1] http://docs.travis-ci.com/user/caching
2015-07-05 00:52:36 -07:00
sudo: false
Add travis-ci configuration
2014-02-22 10:29:21 -07:00
language: c
Travis: Refactor CI files, use container infrastructure. * Split build steps to utilize the Travis build lifecycle. * Move shell code from `.travis.yml` into Bash files in `.ci/`, one file for each step of the Travis build lifecycle. * Use configuration variables in `.travis.yml` to change build behavior (e.g. build 32-bit with `BUILD_32BIT=ON`). * Keep all configuration in environment variables in `.travis.yml`. In scripts, concatenate environment variables according to configuration to change to different behavior. * Add GCC 5 builds for Linux. * Use Travis's caching feature [1] for third-party dependencies and pip packages. * Allow failures MSan, as the errors it reports have to be fixed first. Valgrind is still disabled, but can be enabled by setting `env: VALGRIND=ON` for a job in `.travis.yml`. [1] http://docs.travis-ci.com/user/caching
2015-07-05 00:52:36 -07:00
Configure travis to perform a 32-bit build - Build targeting 32-bit with travis - Code in `before_install`/`after_success` was moved to travis.sh since it provides greater flexibility for detecting the build matrix environment. This improves the build speed since we now install only what's necessary. - Now clint has a dedicated travis worker
2014-04-22 10:40:19 -07:00
env:
travis/coverity: add coverity support Run only on push to branch coverity-scan. We can use a cron script to do this 4 times a week (that's our allowance). NOTE: possible future improvements are: 1. Fold the build matrix item into another short one so we don't overburden travis. It's a little less clear but it should be nicer on the infrastructure. 2. Change the security token, one can do that from the coverity admin page. 3. Don't do the naive `make depend`, but use the prebuilt libraries.
2014-05-31 07:19:14 -07:00
global:
ci/travis: rename $BUILD_NVIM_DEPS to $CACHE_ENABLE
2018-03-11 05:31:10 -07:00
# Set "false" to force rebuild of third-party dependencies.
- CACHE_ENABLE=true
Travis: Refactor CI files, use container infrastructure. * Split build steps to utilize the Travis build lifecycle. * Move shell code from `.travis.yml` into Bash files in `.ci/`, one file for each step of the Travis build lifecycle. * Use configuration variables in `.travis.yml` to change build behavior (e.g. build 32-bit with `BUILD_32BIT=ON`). * Keep all configuration in environment variables in `.travis.yml`. In scripts, concatenate environment variables according to configuration to change to different behavior. * Add GCC 5 builds for Linux. * Use Travis's caching feature [1] for third-party dependencies and pip packages. * Allow failures MSan, as the errors it reports have to be fixed first. Valgrind is still disabled, but can be enabled by setting `env: VALGRIND=ON` for a job in `.travis.yml`. [1] http://docs.travis-ci.com/user/caching
2015-07-05 00:52:36 -07:00
# Build directory for Neovim.
- BUILD_DIR="$TRAVIS_BUILD_DIR/build"
# Build directory for third-party dependencies.
Travis: Cache third-party build directory. Instead of just caching the third-party build output, cache the full build directory. Always run make to ensure that updated dependencies are downloaded.
2015-09-08 03:48:04 -07:00
- DEPS_BUILD_DIR="$HOME/nvim-deps"
# Directory where third-party dependency sources are downloaded to.
- DEPS_DOWNLOAD_DIR="$TRAVIS_BUILD_DIR/deps-downloads"
Travis: Refactor CI files, use container infrastructure. * Split build steps to utilize the Travis build lifecycle. * Move shell code from `.travis.yml` into Bash files in `.ci/`, one file for each step of the Travis build lifecycle. * Use configuration variables in `.travis.yml` to change build behavior (e.g. build 32-bit with `BUILD_32BIT=ON`). * Keep all configuration in environment variables in `.travis.yml`. In scripts, concatenate environment variables according to configuration to change to different behavior. * Add GCC 5 builds for Linux. * Use Travis's caching feature [1] for third-party dependencies and pip packages. * Allow failures MSan, as the errors it reports have to be fixed first. Valgrind is still disabled, but can be enabled by setting `env: VALGRIND=ON` for a job in `.travis.yml`. [1] http://docs.travis-ci.com/user/caching
2015-07-05 00:52:36 -07:00
# Install directory for Neovim.
- INSTALL_PREFIX="$HOME/nvim-install"
# Log directory for Clang sanitizers and Valgrind.
- LOG_DIR="$BUILD_DIR/log"
ci: Dump $NVIM_LOG_FILE contents
2017-05-30 05:54:09 -07:00
# Nvim log file.
- NVIM_LOG_FILE="$BUILD_DIR/.nvimlog"
Travis: Refactor CI files, use container infrastructure. * Split build steps to utilize the Travis build lifecycle. * Move shell code from `.travis.yml` into Bash files in `.ci/`, one file for each step of the Travis build lifecycle. * Use configuration variables in `.travis.yml` to change build behavior (e.g. build 32-bit with `BUILD_32BIT=ON`). * Keep all configuration in environment variables in `.travis.yml`. In scripts, concatenate environment variables according to configuration to change to different behavior. * Add GCC 5 builds for Linux. * Use Travis's caching feature [1] for third-party dependencies and pip packages. * Allow failures MSan, as the errors it reports have to be fixed first. Valgrind is still disabled, but can be enabled by setting `env: VALGRIND=ON` for a job in `.travis.yml`. [1] http://docs.travis-ci.com/user/caching
2015-07-05 00:52:36 -07:00
# Default CMake flags.
- CMAKE_FLAGS="-DTRAVIS_CI_BUILD=ON
-DCMAKE_BUILD_TYPE=Debug
-DCMAKE_INSTALL_PREFIX:PATH=$INSTALL_PREFIX
tests: Rename neovim output handler to nvim
2017-04-09 17:33:00 -07:00
-DBUSTED_OUTPUT_TYPE=nvim
cmake: Pass -DMIN_LOG_LEVEL as compiler definition - Check if MIN_LOG_LEVEL value is a number 0-3, default to INFO (1) or ignore it in Release mode - When TRAVIS_CI_BUILD is ON the default is DEBUG (0) - Add local.mk.example
2014-12-08 13:00:54 -07:00
-DDEPS_PREFIX=$DEPS_BUILD_DIR/usr
log: Always enable; remove DISABLE_LOG - Establish ERROR log level as "critical". Such errors are rare and will be valuable when users encounter unusual circumstances. - Set -DMIN_LOG_LEVEL=3 for release-type builds
2017-05-29 17:03:08 -07:00
-DMIN_LOG_LEVEL=3"
Travis: Cache third-party build directory. Instead of just caching the third-party build output, cache the full build directory. Always run make to ensure that updated dependencies are downloaded.
2015-09-08 03:48:04 -07:00
- DEPS_CMAKE_FLAGS="-DDEPS_DOWNLOAD_DIR:PATH=$DEPS_DOWNLOAD_DIR"
Travis: Refactor CI files, use container infrastructure. * Split build steps to utilize the Travis build lifecycle. * Move shell code from `.travis.yml` into Bash files in `.ci/`, one file for each step of the Travis build lifecycle. * Use configuration variables in `.travis.yml` to change build behavior (e.g. build 32-bit with `BUILD_32BIT=ON`). * Keep all configuration in environment variables in `.travis.yml`. In scripts, concatenate environment variables according to configuration to change to different behavior. * Add GCC 5 builds for Linux. * Use Travis's caching feature [1] for third-party dependencies and pip packages. * Allow failures MSan, as the errors it reports have to be fixed first. Valgrind is still disabled, but can be enabled by setting `env: VALGRIND=ON` for a job in `.travis.yml`. [1] http://docs.travis-ci.com/user/caching
2015-07-05 00:52:36 -07:00
# Additional CMake flags for 32-bit builds.
- CMAKE_FLAGS_32BIT="-DCMAKE_SYSTEM_LIBRARY_PATH=/lib32:/usr/lib32:/usr/local/lib32
-DCMAKE_IGNORE_PATH=/lib:/usr/lib:/usr/local/lib
-DCMAKE_TOOLCHAIN_FILE=$TRAVIS_BUILD_DIR/cmake/i386-linux-gnu.toolchain.cmake"
# Environment variables for Clang sanitizers.
- ASAN_OPTIONS="detect_leaks=1:check_initialization_order=1:log_path=$LOG_DIR/asan"
tsan: Compile with -fPIE and force clang-3.8 This fixes failures with TSAN builds like FATAL: ThreadSanitizer can not mmap the shadow memory (something is mapped at 0x55deea465000 < 0x7cf000000000) FATAL: Make sure to compile with -fPIE and to link with -pie.
2016-11-11 12:18:54 -07:00
- TSAN_OPTIONS="log_path=$LOG_DIR/tsan"
ci: Make ubsan print out a stacktrace when it finds a problem
2016-11-12 20:28:59 -07:00
- UBSAN_OPTIONS="print_stacktrace=1 log_path=$LOG_DIR/ubsan"
Travis: Refactor CI files, use container infrastructure. * Split build steps to utilize the Travis build lifecycle. * Move shell code from `.travis.yml` into Bash files in `.ci/`, one file for each step of the Travis build lifecycle. * Use configuration variables in `.travis.yml` to change build behavior (e.g. build 32-bit with `BUILD_32BIT=ON`). * Keep all configuration in environment variables in `.travis.yml`. In scripts, concatenate environment variables according to configuration to change to different behavior. * Add GCC 5 builds for Linux. * Use Travis's caching feature [1] for third-party dependencies and pip packages. * Allow failures MSan, as the errors it reports have to be fixed first. Valgrind is still disabled, but can be enabled by setting `env: VALGRIND=ON` for a job in `.travis.yml`. [1] http://docs.travis-ci.com/user/caching
2015-07-05 00:52:36 -07:00
# Environment variables for Valgrind.
- VALGRIND_LOG="$LOG_DIR/valgrind-%p.log"
ci/travis: rename $BUILD_NVIM_DEPS to $CACHE_ENABLE
2018-03-11 05:31:10 -07:00
# If this file exists, the cache is valid (compile was successful).
Travis: Refactor CI files, use container infrastructure. * Split build steps to utilize the Travis build lifecycle. * Move shell code from `.travis.yml` into Bash files in `.ci/`, one file for each step of the Travis build lifecycle. * Use configuration variables in `.travis.yml` to change build behavior (e.g. build 32-bit with `BUILD_32BIT=ON`). * Keep all configuration in environment variables in `.travis.yml`. In scripts, concatenate environment variables according to configuration to change to different behavior. * Add GCC 5 builds for Linux. * Use Travis's caching feature [1] for third-party dependencies and pip packages. * Allow failures MSan, as the errors it reports have to be fixed first. Valgrind is still disabled, but can be enabled by setting `env: VALGRIND=ON` for a job in `.travis.yml`. [1] http://docs.travis-ci.com/user/caching
2015-07-05 00:52:36 -07:00
- CACHE_MARKER="$HOME/.cache/nvim-deps/.travis_cache_marker"
Add travis build for lua functionaltest
2016-03-06 22:18:44 -07:00
# default target name for functional tests
- FUNCTIONALTEST=functionaltest
ci: Refactor CI scripts 1. CI_TARGET now determines which run_${CI_TARGET}.sh script to use. Defaults to `tests`. 2. Build no longer halts on the first failing suit: e.g. if functional tests failed it will continue with unit tests, etc. 3. All ${MAKE_CMD} occurrences moved to `top_make` function, added `build_make` as an alias to `make -C build` (`"${MAKE_CMD}" -C "${BUILD_DIR}"`) which is too verbose. `suite.sh` was copied from powerline (tests/common.sh file), assumes running with POSIX shells (and actually uses dash in powerline). Then some convenience functions were added (run_test and below).
2017-03-31 06:02:53 -07:00
- CI_TARGET=tests
Travis: Refactor CI files, use container infrastructure. * Split build steps to utilize the Travis build lifecycle. * Move shell code from `.travis.yml` into Bash files in `.ci/`, one file for each step of the Travis build lifecycle. * Use configuration variables in `.travis.yml` to change build behavior (e.g. build 32-bit with `BUILD_32BIT=ON`). * Keep all configuration in environment variables in `.travis.yml`. In scripts, concatenate environment variables according to configuration to change to different behavior. * Add GCC 5 builds for Linux. * Use Travis's caching feature [1] for third-party dependencies and pip packages. * Allow failures MSan, as the errors it reports have to be fixed first. Valgrind is still disabled, but can be enabled by setting `env: VALGRIND=ON` for a job in `.travis.yml`. [1] http://docs.travis-ci.com/user/caching
2015-07-05 00:52:36 -07:00
ci: Enable staged builds (#6739) This should better allow distributing the load among PRs, while getting critical feedback to the submitter sooner. First stage runs the ASAN/UBSAN/TSAN since any failures in those are gating issues. Second stage runs the rest of the normal builds in parallel. Remaining stages provide lower priority feedback. The lint build runs fast locally, so it's better to run that locally than wait on CI. The coverage build is pretty fickle, so it is only run once all other jobs are green.
2017-05-13 21:46:30 -07:00
jobs:
Travis: Prepare for OS X builds. * Use bot-ci script at to set up prebuilt dependencies. * Make CI scripts more consistent.
2014-11-27 07:10:36 -07:00
include:
travis: Reduce stages to flaky builds (gcov, tsan) and everything else Separating the non-flaky builds (asan, normal builds, lint) into separate stages simply slowed down overall CI turnaround. Since none of the builds rely on the output of others, reducing the stages increases the opportunities for parallel builds.
2018-01-01 19:30:54 -07:00
- stage: normal builds
ci: Enable staged builds (#6739) This should better allow distributing the load among PRs, while getting critical feedback to the submitter sooner. First stage runs the ASAN/UBSAN/TSAN since any failures in those are gating issues. Second stage runs the rest of the normal builds in parallel. Remaining stages provide lower priority feedback. The lint build runs fast locally, so it's better to run that locally than wait on CI. The coverage build is pretty fickle, so it is only run once all other jobs are green.
2017-05-13 21:46:30 -07:00
os: linux
travis: Use Ubuntu's clang instead of llvm's repo The llvm repos commonly have access issues, so removing them will improve stability of the Travis builds. Filtering check_log's output through asan_symbolize also avoids the version dance every time a new clang version makes its way into Travis.
2018-01-01 19:00:07 -07:00
compiler: clang
ci: Enable staged builds (#6739) This should better allow distributing the load among PRs, while getting critical feedback to the submitter sooner. First stage runs the ASAN/UBSAN/TSAN since any failures in those are gating issues. Second stage runs the rest of the normal builds in parallel. Remaining stages provide lower priority feedback. The lint build runs fast locally, so it's better to run that locally than wait on CI. The coverage build is pretty fickle, so it is only run once all other jobs are green.
2017-05-13 21:46:30 -07:00
env: >
CLANG_SANITIZER=ASAN_UBSAN
CMAKE_FLAGS="$CMAKE_FLAGS -DPREFER_LUA=ON"
ci/travis: require "sudo" for ASAN_UBSAN build Workaround for this fun new issue: ==27404==LeakSanitizer has encountered a fatal error. ==27404==HINT: For debugging, try setting environment variable LSAN_OPTIONS=verbosity=1:log_threads=1 ==27404==HINT: LeakSanitizer does not work under ptrace (strace, gdb, etc) Failed: E /build|logs :: Runtime errors detected. https://github.com/travis-ci/travis-ci/issues/9033 https://github.com/google/sanitizers/issues/764
2018-01-10 15:21:30 -07:00
sudo: true
travis: Reduce stages to flaky builds (gcov, tsan) and everything else Separating the non-flaky builds (asan, normal builds, lint) into separate stages simply slowed down overall CI turnaround. Since none of the builds rely on the output of others, reducing the stages increases the opportunities for parallel builds.
2018-01-01 19:30:54 -07:00
- os: linux
travis: Remove ubuntu-r-toolchain/test ppa Use unversioned gcc/gcov commands rather than pulling in a separate repo.
2018-01-01 19:19:58 -07:00
compiler: gcc
travis: Disable LuaJIT for functionaltest-lua build Since we're already using Lua for the testing this allows us to ensure our build still works properly without LuaJIT available.
2018-02-01 06:48:52 -07:00
env: >
FUNCTIONALTEST=functionaltest-lua
CMAKE_FLAGS="$CMAKE_FLAGS -DPREFER_LUA=ON"
DEPS_CMAKE_FLAGS="$DEPS_CMAKE_FLAGS -DUSE_BUNDLED_LUAJIT=OFF"
Travis: Refactor CI files, use container infrastructure. * Split build steps to utilize the Travis build lifecycle. * Move shell code from `.travis.yml` into Bash files in `.ci/`, one file for each step of the Travis build lifecycle. * Use configuration variables in `.travis.yml` to change build behavior (e.g. build 32-bit with `BUILD_32BIT=ON`). * Keep all configuration in environment variables in `.travis.yml`. In scripts, concatenate environment variables according to configuration to change to different behavior. * Add GCC 5 builds for Linux. * Use Travis's caching feature [1] for third-party dependencies and pip packages. * Allow failures MSan, as the errors it reports have to be fixed first. Valgrind is still disabled, but can be enabled by setting `env: VALGRIND=ON` for a job in `.travis.yml`. [1] http://docs.travis-ci.com/user/caching
2015-07-05 00:52:36 -07:00
- os: linux
ci/travis: require "sudo" for ASAN_UBSAN build Workaround for this fun new issue: ==27404==LeakSanitizer has encountered a fatal error. ==27404==HINT: For debugging, try setting environment variable LSAN_OPTIONS=verbosity=1:log_threads=1 ==27404==HINT: LeakSanitizer does not work under ptrace (strace, gdb, etc) Failed: E /build|logs :: Runtime errors detected. https://github.com/travis-ci/travis-ci/issues/9033 https://github.com/google/sanitizers/issues/764
2018-01-10 15:21:30 -07:00
# Travis creates a cache per compiler. Set a different value here to
# store 32-bit dependencies in a separate cache.
travis: Remove ubuntu-r-toolchain/test ppa Use unversioned gcc/gcov commands rather than pulling in a separate repo.
2018-01-01 19:19:58 -07:00
compiler: gcc -m32
CI/travis: enable gcov for one build only. #3926
2016-01-01 19:00:20 -07:00
env: BUILD_32BIT=ON
Travis: Prepare for OS X builds. * Use bot-ci script at to set up prebuilt dependencies. * Make CI scripts more consistent.
2014-11-27 07:10:36 -07:00
- os: osx
Travis: Fix OS X builds.
2014-11-30 03:27:08 -07:00
compiler: clang
ci: .travis.yml: Minimize scope of osx_image directive. (#5420)
2016-10-01 18:37:17 -07:00
osx_image: xcode7.3 # macOS 10.11
Travis: Prepare for OS X builds. * Use bot-ci script at to set up prebuilt dependencies. * Make CI scripts more consistent.
2014-11-27 07:10:36 -07:00
- os: osx
travis: Remove ubuntu-r-toolchain/test ppa Use unversioned gcc/gcov commands rather than pulling in a separate repo.
2018-01-01 19:19:58 -07:00
compiler: gcc
ci: .travis.yml: Minimize scope of osx_image directive. (#5420)
2016-10-01 18:37:17 -07:00
osx_image: xcode7.3 # macOS 10.11
travis: Reduce stages to flaky builds (gcov, tsan) and everything else Separating the non-flaky builds (asan, normal builds, lint) into separate stages simply slowed down overall CI turnaround. Since none of the builds rely on the output of others, reducing the stages increases the opportunities for parallel builds.
2018-01-01 19:30:54 -07:00
- os: linux
ci: Enable staged builds (#6739) This should better allow distributing the load among PRs, while getting critical feedback to the submitter sooner. First stage runs the ASAN/UBSAN/TSAN since any failures in those are gating issues. Second stage runs the rest of the normal builds in parallel. Remaining stages provide lower priority feedback. The lint build runs fast locally, so it's better to run that locally than wait on CI. The coverage build is pretty fickle, so it is only run once all other jobs are green.
2017-05-13 21:46:30 -07:00
env: CI_TARGET=lint
travis: Move TSAN to last stage and allow failure TSAN build has been much less reliable lately, so it shouldn't hold up the other tests.
2017-08-13 07:01:39 -07:00
- stage: Flaky builds
ci: Enable staged builds (#6739) This should better allow distributing the load among PRs, while getting critical feedback to the submitter sooner. First stage runs the ASAN/UBSAN/TSAN since any failures in those are gating issues. Second stage runs the rest of the normal builds in parallel. Remaining stages provide lower priority feedback. The lint build runs fast locally, so it's better to run that locally than wait on CI. The coverage build is pretty fickle, so it is only run once all other jobs are green.
2017-05-13 21:46:30 -07:00
os: linux
travis: Remove ubuntu-r-toolchain/test ppa Use unversioned gcc/gcov commands rather than pulling in a separate repo.
2018-01-01 19:19:58 -07:00
compiler: gcc
env: GCOV=gcov CMAKE_FLAGS="$CMAKE_FLAGS -DUSE_GCOV=ON"
travis: Move TSAN to last stage and allow failure TSAN build has been much less reliable lately, so it shouldn't hold up the other tests.
2017-08-13 07:01:39 -07:00
- os: linux
travis: Use Ubuntu's clang instead of llvm's repo The llvm repos commonly have access issues, so removing them will improve stability of the Travis builds. Filtering check_log's output through asan_symbolize also avoids the version dance every time a new clang version makes its way into Travis.
2018-01-01 19:00:07 -07:00
compiler: clang
travis: Move TSAN to last stage and allow failure TSAN build has been much less reliable lately, so it shouldn't hold up the other tests.
2017-08-13 07:01:39 -07:00
env: CLANG_SANITIZER=TSAN
CI: allow GCOV build to fail
2016-12-27 16:00:52 -07:00
allow_failures:
travis: Remove ubuntu-r-toolchain/test ppa Use unversioned gcc/gcov commands rather than pulling in a separate repo.
2018-01-01 19:19:58 -07:00
- env: GCOV=gcov CMAKE_FLAGS="$CMAKE_FLAGS -DUSE_GCOV=ON"
travis: Move TSAN to last stage and allow failure TSAN build has been much less reliable lately, so it shouldn't hold up the other tests.
2017-08-13 07:01:39 -07:00
- env: CLANG_SANITIZER=TSAN
Travis: Fail fast, disable JIT for functional tests. Disable JIT to find cause for random `PANIC: unprotected error in call to Lua API` on Travis (OS X).
2015-02-02 09:19:12 -07:00
fast_finish: true
Travis: Refactor CI files, use container infrastructure. * Split build steps to utilize the Travis build lifecycle. * Move shell code from `.travis.yml` into Bash files in `.ci/`, one file for each step of the Travis build lifecycle. * Use configuration variables in `.travis.yml` to change build behavior (e.g. build 32-bit with `BUILD_32BIT=ON`). * Keep all configuration in environment variables in `.travis.yml`. In scripts, concatenate environment variables according to configuration to change to different behavior. * Add GCC 5 builds for Linux. * Use Travis's caching feature [1] for third-party dependencies and pip packages. * Allow failures MSan, as the errors it reports have to be fixed first. Valgrind is still disabled, but can be enabled by setting `env: VALGRIND=ON` for a job in `.travis.yml`. [1] http://docs.travis-ci.com/user/caching
2015-07-05 00:52:36 -07:00
ci: Do not hide ci directory (#6410)
2017-03-31 05:32:58 -07:00
before_install: ci/before_install.sh
install: ci/install.sh
before_script: ci/before_script.sh
script: ci/script.sh
before_cache: ci/before_cache.sh
after_success: ci/after_success.sh
Travis: Refactor CI files, use container infrastructure. * Split build steps to utilize the Travis build lifecycle. * Move shell code from `.travis.yml` into Bash files in `.ci/`, one file for each step of the Travis build lifecycle. * Use configuration variables in `.travis.yml` to change build behavior (e.g. build 32-bit with `BUILD_32BIT=ON`). * Keep all configuration in environment variables in `.travis.yml`. In scripts, concatenate environment variables according to configuration to change to different behavior. * Add GCC 5 builds for Linux. * Use Travis's caching feature [1] for third-party dependencies and pip packages. * Allow failures MSan, as the errors it reports have to be fixed first. Valgrind is still disabled, but can be enabled by setting `env: VALGRIND=ON` for a job in `.travis.yml`. [1] http://docs.travis-ci.com/user/caching
2015-07-05 00:52:36 -07:00
addons:
apt:
packages:
- autoconf
- automake
ci: Better core dump checking - Do not exclude any directories from `find` search, remove dumps before tests instead. - Install `apport` on travis so that linux tests should produce core dumps (based on information from travis-ci/travis-ci#3754, not sure whether it still applies). - Check cores in lua so that one has an idea which test is failing exactly. Do this only 10% of time on linux because traversing the file system is slow. Unit tests are still not touched, though it is what `app` argument in `check_cores` is for. TODO? consider using `find`, it may be faster. Consider retiring `os.execute`, dealing with escaping is bad.
2016-11-04 08:20:58 -07:00
- apport
Travis: Refactor CI files, use container infrastructure. * Split build steps to utilize the Travis build lifecycle. * Move shell code from `.travis.yml` into Bash files in `.ci/`, one file for each step of the Travis build lifecycle. * Use configuration variables in `.travis.yml` to change build behavior (e.g. build 32-bit with `BUILD_32BIT=ON`). * Keep all configuration in environment variables in `.travis.yml`. In scripts, concatenate environment variables according to configuration to change to different behavior. * Add GCC 5 builds for Linux. * Use Travis's caching feature [1] for third-party dependencies and pip packages. * Allow failures MSan, as the errors it reports have to be fixed first. Valgrind is still disabled, but can be enabled by setting `env: VALGRIND=ON` for a job in `.travis.yml`. [1] http://docs.travis-ci.com/user/caching
2015-07-05 00:52:36 -07:00
- build-essential
travis: Use Ubuntu's clang instead of llvm's repo The llvm repos commonly have access issues, so removing them will improve stability of the Travis builds. Filtering check_log's output through asan_symbolize also avoids the version dance every time a new clang version makes its way into Travis.
2018-01-01 19:00:07 -07:00
- clang
Travis: Install Python 3 to run Python 3 tests. Install Python 3.3 from the Deadsnakes PPA. As this doesn't have pip, install it manually into ~/.local. ~/.local/bin is apparently in Travis's default PATH, meaning "pip" doesn't refer to Python 2's pip anymore, but to the manually installed Python 3 version. Updated the scripts to use version- suffixed executable names (e.g. pip2.7). Set CC=cc to use system's default compiler when installing Python modules, as gcc on OS X had a problem with compiling one of the dependencies of the Neovim Python module.
2015-09-22 05:36:15 -07:00
- cmake
ci: Install cscope, remove deadsnakes PPA The travis ubuntu "trusty" image already pre-installs python 3.5. https://docs.travis-ci.com/user/trusty-ci-environment
2016-12-24 15:24:57 -07:00
- cscope
Travis: Refactor CI files, use container infrastructure. * Split build steps to utilize the Travis build lifecycle. * Move shell code from `.travis.yml` into Bash files in `.ci/`, one file for each step of the Travis build lifecycle. * Use configuration variables in `.travis.yml` to change build behavior (e.g. build 32-bit with `BUILD_32BIT=ON`). * Keep all configuration in environment variables in `.travis.yml`. In scripts, concatenate environment variables according to configuration to change to different behavior. * Add GCC 5 builds for Linux. * Use Travis's caching feature [1] for third-party dependencies and pip packages. * Allow failures MSan, as the errors it reports have to be fixed first. Valgrind is still disabled, but can be enabled by setting `env: VALGRIND=ON` for a job in `.travis.yml`. [1] http://docs.travis-ci.com/user/caching
2015-07-05 00:52:36 -07:00
- g++-multilib
- gcc-multilib
Travis: Install Python 3 to run Python 3 tests. Install Python 3.3 from the Deadsnakes PPA. As this doesn't have pip, install it manually into ~/.local. ~/.local/bin is apparently in Travis's default PATH, meaning "pip" doesn't refer to Python 2's pip anymore, but to the manually installed Python 3 version. Updated the scripts to use version- suffixed executable names (e.g. pip2.7). Set CC=cc to use system's default compiler when installing Python modules, as gcc on OS X had a problem with compiling one of the dependencies of the Neovim Python module.
2015-09-22 05:36:15 -07:00
- gdb
ci: install Turkish locale and make locale tests more reliable
2017-04-10 10:48:45 -07:00
- language-pack-tr
Travis: Refactor CI files, use container infrastructure. * Split build steps to utilize the Travis build lifecycle. * Move shell code from `.travis.yml` into Bash files in `.ci/`, one file for each step of the Travis build lifecycle. * Use configuration variables in `.travis.yml` to change build behavior (e.g. build 32-bit with `BUILD_32BIT=ON`). * Keep all configuration in environment variables in `.travis.yml`. In scripts, concatenate environment variables according to configuration to change to different behavior. * Add GCC 5 builds for Linux. * Use Travis's caching feature [1] for third-party dependencies and pip packages. * Allow failures MSan, as the errors it reports have to be fixed first. Valgrind is still disabled, but can be enabled by setting `env: VALGRIND=ON` for a job in `.travis.yml`. [1] http://docs.travis-ci.com/user/caching
2015-07-05 00:52:36 -07:00
- libc6-dev-i386
Travis: Install Python 3 to run Python 3 tests. Install Python 3.3 from the Deadsnakes PPA. As this doesn't have pip, install it manually into ~/.local. ~/.local/bin is apparently in Travis's default PATH, meaning "pip" doesn't refer to Python 2's pip anymore, but to the manually installed Python 3 version. Updated the scripts to use version- suffixed executable names (e.g. pip2.7). Set CC=cc to use system's default compiler when installing Python modules, as gcc on OS X had a problem with compiling one of the dependencies of the Neovim Python module.
2015-09-22 05:36:15 -07:00
- libtool
ci: install Turkish locale and make locale tests more reliable
2017-04-10 10:48:45 -07:00
- locales
ci/travis: use ninja instead of make
2018-03-09 12:55:10 -07:00
- ninja-build
Travis: Install Python 3 to run Python 3 tests. Install Python 3.3 from the Deadsnakes PPA. As this doesn't have pip, install it manually into ~/.local. ~/.local/bin is apparently in Travis's default PATH, meaning "pip" doesn't refer to Python 2's pip anymore, but to the manually installed Python 3 version. Updated the scripts to use version- suffixed executable names (e.g. pip2.7). Set CC=cc to use system's default compiler when installing Python modules, as gcc on OS X had a problem with compiling one of the dependencies of the Neovim Python module.
2015-09-22 05:36:15 -07:00
- pkg-config
- unzip
Travis: Refactor CI files, use container infrastructure. * Split build steps to utilize the Travis build lifecycle. * Move shell code from `.travis.yml` into Bash files in `.ci/`, one file for each step of the Travis build lifecycle. * Use configuration variables in `.travis.yml` to change build behavior (e.g. build 32-bit with `BUILD_32BIT=ON`). * Keep all configuration in environment variables in `.travis.yml`. In scripts, concatenate environment variables according to configuration to change to different behavior. * Add GCC 5 builds for Linux. * Use Travis's caching feature [1] for third-party dependencies and pip packages. * Allow failures MSan, as the errors it reports have to be fixed first. Valgrind is still disabled, but can be enabled by setting `env: VALGRIND=ON` for a job in `.travis.yml`. [1] http://docs.travis-ci.com/user/caching
2015-07-05 00:52:36 -07:00
- valgrind
Travis: Install Python 3 to run Python 3 tests. Install Python 3.3 from the Deadsnakes PPA. As this doesn't have pip, install it manually into ~/.local. ~/.local/bin is apparently in Travis's default PATH, meaning "pip" doesn't refer to Python 2's pip anymore, but to the manually installed Python 3 version. Updated the scripts to use version- suffixed executable names (e.g. pip2.7). Set CC=cc to use system's default compiler when installing Python modules, as gcc on OS X had a problem with compiling one of the dependencies of the Neovim Python module.
2015-09-22 05:36:15 -07:00
- xclip
Travis: Refactor CI files, use container infrastructure. * Split build steps to utilize the Travis build lifecycle. * Move shell code from `.travis.yml` into Bash files in `.ci/`, one file for each step of the Travis build lifecycle. * Use configuration variables in `.travis.yml` to change build behavior (e.g. build 32-bit with `BUILD_32BIT=ON`). * Keep all configuration in environment variables in `.travis.yml`. In scripts, concatenate environment variables according to configuration to change to different behavior. * Add GCC 5 builds for Linux. * Use Travis's caching feature [1] for third-party dependencies and pip packages. * Allow failures MSan, as the errors it reports have to be fixed first. Valgrind is still disabled, but can be enabled by setting `env: VALGRIND=ON` for a job in `.travis.yml`. [1] http://docs.travis-ci.com/user/caching
2015-07-05 00:52:36 -07:00
branches:
except:
- nightly
cache:
apt: true
directories:
- "$HOME/.cache/pip"
- "$HOME/.cache/nvim-deps"
ci/travis: also cache $DEPS_DOWNLOAD_DIR ref #5166
2018-03-15 23:29:43 -07:00
- "$HOME/.cache/nvim-deps-downloads"
Travis: Refactor CI files, use container infrastructure. * Split build steps to utilize the Travis build lifecycle. * Move shell code from `.travis.yml` into Bash files in `.ci/`, one file for each step of the Travis build lifecycle. * Use configuration variables in `.travis.yml` to change build behavior (e.g. build 32-bit with `BUILD_32BIT=ON`). * Keep all configuration in environment variables in `.travis.yml`. In scripts, concatenate environment variables according to configuration to change to different behavior. * Add GCC 5 builds for Linux. * Use Travis's caching feature [1] for third-party dependencies and pip packages. * Allow failures MSan, as the errors it reports have to be fixed first. Valgrind is still disabled, but can be enabled by setting `env: VALGRIND=ON` for a job in `.travis.yml`. [1] http://docs.travis-ci.com/user/caching
2015-07-05 00:52:36 -07:00
travis: Configure to notify gitter chat room
2015-03-17 16:36:45 -07:00
notifications:
webhooks:
urls:
- https://webhooks.gitter.im/e/b5c38c99f9677aa3d031
Reference in New Issue Copy Permalink