neovim/.travis.yml

language: c
env:
  - TRAVIS_BUILD_TYPE=clang/asan
  - TRAVIS_BUILD_TYPE=gcc/ia32
  - TRAVIS_BUILD_TYPE=gcc/unittest
  - TRAVIS_BUILD_TYPE=clint
  - TRAVIS_BUILD_TYPE=api/python
script:
  - ./scripts/travis.sh
Add travis-ci configuration 2014-02-22 10:29:21 -07:00			`language: c`
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_BUILD_TYPE=clang/asan`
			`- TRAVIS_BUILD_TYPE=gcc/ia32`
			`- TRAVIS_BUILD_TYPE=gcc/unittest`
			`- TRAVIS_BUILD_TYPE=clint`
API: Test: Setup basic test infrastructure - Add a 'expect' utility script that can run simple API tests using clients developed for any platform. - Extend travis build matrix to run API tests using the python client and valgrind. This script can be used to write API tests without having to manage nvim's lifetime: - It starts a single nvim instance listening on a known socket - Invokes the test runner, which should connect to NEOVIM_LISTEN_ADDRESS - The nvim instance started by the script provides a `BeforeEachTest` function, which should be called before each test to reset nvim to a clean state. - It takes care of shutting down nvim once the tests are finished. As explained [here](https://github.com/neovim/neovim/pull/737#issuecomment-43941520), it's not possible to fully reset nvim to it's initial state, but the `BeforeEachTest` function should be enough for most test cases. Tests requiring a fully clean nvim instance should take care of starting/stopping nvim. 2014-05-23 11:49:51 -07:00			`- TRAVIS_BUILD_TYPE=api/python`
Refactor travis build to use clang's sanitizers - Valgrind configuration removed - Fix errors reported by the undefined behavior sanitizer - Travis will now run two build steps: - A normal build of a shared library for unit testing(in parallel with gcc) - A clang build with some sanitizers enabled for integration testing. After these changes travis will run much faster, while providing valgrind-like error detection. 2014-03-13 08:11:03 -07:00			`script:`
			`- ./scripts/travis.sh`