UltiSnips/.travis.yml

language: python

python:
  - 2.7
  - 3.3
  - 3.4
env:
  - VIM_VERSION="74"
  - VIM_VERSION="mercurial"
  - VIM_VERSION="NEOVIM"

install:
   # Some of these commands fail transiently. We keep retrying them until they succeed.
   - until sudo add-apt-repository ppa:kalakris/tmux -y; do sleep 10; done
   - until sudo add-apt-repository ppa:neovim-ppa/unstable -y; do sleep 10; done
   - until sudo apt-get update -qq; do sleep 10; done
   - until sudo apt-get install -qq -y --force-yes tmux xclip gdb neovim mercurial; do sleep 10; done
   - ./travis_install.sh

script:
   - ./travis_test.sh
A travis script. 2015-02-14 08:38:17 -05:00			`language: python`

			`python:`
			`- 2.7`
Started to test py2 and py3 on travis now. I also learned that Vim 7.3 does not seem to be working at all anymore. Fixes a bug that only happens with python3. 2015-04-18 11:15:05 -04:00			`- 3.3`
			`- 3.4`
			`env:`
			`- VIM_VERSION="74"`
Fix testing and test against more scenarios. Before this, we only ever ran against system python preinstalled on travis (i.e. 2.7 and 3.2). This change makes sure that Vim is always build and run against the correct python version in the virtual env. Also adds mercurial (HEAD) Vim as a testing target. This patch took me forever to get right. At least 2 months and ~200 travis runs of trial and error - there is just too much finicky going on with the many virtual envs on travis, Vims strange build system that does not use python-config and LD_LIBRARY_PATH loading. En plus, the debugging insights one can glance from travis runs are rather limited. Detailed changes: - Uses less sudo and only outside of scripts. - Build correct version of Vim against correct version of Python. This needs some LD_LIBRARY_PATH magic to make sure that Vim finds the correct Python libraries at runtime. - Removes dirty hack that overwrote /usr/bin/vim with the correct Vim version to run. The test_all.py script now takes the Vim binary as a parameter. 2015-07-03 15:52:50 -04:00			`- VIM_VERSION="mercurial"`
Add a testing interface that works for Neovim. - Remove support for python 3.2 to reduce number of test cases and because it actually fails with Neovim. It is not a supported version anyways. - Due to Neovim not handling fast typing through the console properly (https://github.com/neovim/neovim/issues/2454), the typing is actually simulated through the Python client. We need to differentiate now if a keystroke is meant for the terminal or for the Vim session. Using neovim.input() introduces additional chances for races since inputs are not buffered but processed right away. This results in more retries for some tests. - Neovim needs more parameters and configuration passed in through the test script. Added command line arguments for these. - Skip an extra test under Neovim due to https://github.com/neovim/python-client/issues/128. 2015-07-14 15:58:30 -04:00			`- VIM_VERSION="NEOVIM"`
Started to test py2 and py3 on travis now. I also learned that Vim 7.3 does not seem to be working at all anymore. Fixes a bug that only happens with python3. 2015-04-18 11:15:05 -04:00
Fix testing and test against more scenarios. Before this, we only ever ran against system python preinstalled on travis (i.e. 2.7 and 3.2). This change makes sure that Vim is always build and run against the correct python version in the virtual env. Also adds mercurial (HEAD) Vim as a testing target. This patch took me forever to get right. At least 2 months and ~200 travis runs of trial and error - there is just too much finicky going on with the many virtual envs on travis, Vims strange build system that does not use python-config and LD_LIBRARY_PATH loading. En plus, the debugging insights one can glance from travis runs are rather limited. Detailed changes: - Uses less sudo and only outside of scripts. - Build correct version of Vim against correct version of Python. This needs some LD_LIBRARY_PATH magic to make sure that Vim finds the correct Python libraries at runtime. - Removes dirty hack that overwrote /usr/bin/vim with the correct Vim version to run. The test_all.py script now takes the Vim binary as a parameter. 2015-07-03 15:52:50 -04:00			`install:`
			`# Some of these commands fail transiently. We keep retrying them until they succeed.`
			`- until sudo add-apt-repository ppa:kalakris/tmux -y; do sleep 10; done`
			`- until sudo add-apt-repository ppa:neovim-ppa/unstable -y; do sleep 10; done`
			`- until sudo apt-get update -qq; do sleep 10; done`
			`- until sudo apt-get install -qq -y --force-yes tmux xclip gdb neovim mercurial; do sleep 10; done`
			`- ./travis_install.sh`
Started to test py2 and py3 on travis now. I also learned that Vim 7.3 does not seem to be working at all anymore. Fixes a bug that only happens with python3. 2015-04-18 11:15:05 -04:00
Fix testing and test against more scenarios. Before this, we only ever ran against system python preinstalled on travis (i.e. 2.7 and 3.2). This change makes sure that Vim is always build and run against the correct python version in the virtual env. Also adds mercurial (HEAD) Vim as a testing target. This patch took me forever to get right. At least 2 months and ~200 travis runs of trial and error - there is just too much finicky going on with the many virtual envs on travis, Vims strange build system that does not use python-config and LD_LIBRARY_PATH loading. En plus, the debugging insights one can glance from travis runs are rather limited. Detailed changes: - Uses less sudo and only outside of scripts. - Build correct version of Vim against correct version of Python. This needs some LD_LIBRARY_PATH magic to make sure that Vim finds the correct Python libraries at runtime. - Removes dirty hack that overwrote /usr/bin/vim with the correct Vim version to run. The test_all.py script now takes the Vim binary as a parameter. 2015-07-03 15:52:50 -04:00			`script:`
			`- ./travis_test.sh`