neovim/.ci/run_tests.sh

#!/usr/bin/env bash

set -e
set -o pipefail

CI_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
source "${CI_DIR}/common/build.sh"
source "${CI_DIR}/common/test.sh"

build_nvim

if [ "$CLANG_SANITIZER" != "TSAN" ]; then
  # Additional threads are only created when the builtin UI starts, which
  # doesn't happen in the unit/functional tests
  run_unittests
  run_functionaltests
fi
run_oldtests

install_nvim

touch "${SUCCESS_MARKER}"
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			`#!/usr/bin/env bash`

			`set -e`
			`set -o pipefail`

			`CI_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"`
			`source "${CI_DIR}/common/build.sh"`
			`source "${CI_DIR}/common/test.sh"`

			`build_nvim`

travis: Enable TSAN for sanity checking the terminal UI 2015-08-28 08:29:15 -07:00			`if [ "$CLANG_SANITIZER" != "TSAN" ]; then`
			`# Additional threads are only created when the builtin UI starts, which`
			`# doesn't happen in the unit/functional tests`
			`run_unittests`
			`run_functionaltests`
			`fi`
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			`run_oldtests`

			`install_nvim`

			`touch "${SUCCESS_MARKER}"`