p53209761
/
test_ok2
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
test_ok2/appveyor.yml

45 lines
1.2 KiB
YAML
Raw Normal View History

Test with pypy and enable coveralls in AppVeyor * Install pypy using chocolatey * Enable coveralls test environment in AppVeyor * Suggest maintaining build matrix in .travis.yml by using "tox --listenvs" Fix #1254
2016-01-31 06:48:15 +08:00
environment:
COVERALLS_REPO_TOKEN:
secure: 2NJ5Ct55cHJ9WEg3xbSqCuv0rdgzzb6pnzOIG5OkMbTndw3wOBrXntWFoQrXiMFi
# this is pytest's token in coveralls.io, encrypted
# using pytestbot account as detailed here:
# https://www.appveyor.com/docs/build-configuration#secure-variables
Split AppVeyor test runs in multiple jobs to avoid timeout issues Some of our builds have been timing out (over 1 hour), on AppVeyor
2016-07-05 08:50:05 +08:00
matrix:
Only execute "coveralls" toxenv on master once Just noticed that the "coveralls" env was being execute after each env. This was introduced by mistake in #2056
2016-11-25 02:08:51 +08:00
# coveralls is not in the default env list
- TOXENV: "coveralls"
Only install pypy on AppVeyor for "pypy" tox-env
2016-11-12 22:29:40 +08:00
# note: please use "tox --listenvs" to populate the build matrix below
Use one job for each tox env on AppVeyor Some time ago when we first added support for testing pytest on AppVeyor, jobs in a build would not start immediately one after the other, as if AppVeyor would schedule jobs from other builds (projects) in its VMs. So it made sense at the time to reduce the number of jobs. I have noticed in other projects that this behavior has changed, and jobs in a build now start one after the other. Having a separate list then improves visibility when the build fails, because we can see at a glance the failing(s) tox environment(s).
2016-11-12 21:50:22 +08:00
- TOXENV: "linting"
- TOXENV: "py26"
- TOXENV: "py27"
- TOXENV: "py33"
- TOXENV: "py34"
- TOXENV: "py35"
Add py36 to test on AppVeyor Fix #2134
2017-01-06 05:18:03 +08:00
- TOXENV: "py36"
Allow failure of pypy on AppVeyor Related to #1963
2016-11-12 05:17:14 +08:00
- TOXENV: "pypy"
Use one job for each tox env on AppVeyor Some time ago when we first added support for testing pytest on AppVeyor, jobs in a build would not start immediately one after the other, as if AppVeyor would schedule jobs from other builds (projects) in its VMs. So it made sense at the time to reduce the number of jobs. I have noticed in other projects that this behavior has changed, and jobs in a build now start one after the other. Having a separate list then improves visibility when the build fails, because we can see at a glance the failing(s) tox environment(s).
2016-11-12 21:50:22 +08:00
- TOXENV: "py27-pexpect"
- TOXENV: "py27-xdist"
- TOXENV: "py27-trial"
Only test numpy with py27 and py35. Travis was not successfully installing numpy with python<=2.6, python<=3.3, or PyPy. I decided that it didn't make sense to use numpy for all the tests, so instead I made new testing environments specifically for numpy.
2017-06-16 09:41:13 +08:00
- TOXENV: "py27-numpy"
Use py36 as preferred Python 3 interpreter for CI testing
2017-08-15 06:28:54 +08:00
- TOXENV: "py36-pexpect"
- TOXENV: "py36-xdist"
- TOXENV: "py36-trial"
- TOXENV: "py36-numpy"
Use one job for each tox env on AppVeyor Some time ago when we first added support for testing pytest on AppVeyor, jobs in a build would not start immediately one after the other, as if AppVeyor would schedule jobs from other builds (projects) in its VMs. So it made sense at the time to reduce the number of jobs. I have noticed in other projects that this behavior has changed, and jobs in a build now start one after the other. Having a separate list then improves visibility when the build fails, because we can see at a glance the failing(s) tox environment(s).
2016-11-12 21:50:22 +08:00
- TOXENV: "py27-nobyte"
- TOXENV: "doctesting"
Use py36 as preferred Python 3 interpreter for CI testing
2017-08-15 06:28:54 +08:00
- TOXENV: "py35-freeze"
Use one job for each tox env on AppVeyor Some time ago when we first added support for testing pytest on AppVeyor, jobs in a build would not start immediately one after the other, as if AppVeyor would schedule jobs from other builds (projects) in its VMs. So it made sense at the time to reduce the number of jobs. I have noticed in other projects that this behavior has changed, and jobs in a build now start one after the other. Having a separate list then improves visibility when the build fails, because we can see at a glance the failing(s) tox environment(s).
2016-11-12 21:50:22 +08:00
- TOXENV: "docs"
Split AppVeyor test runs in multiple jobs to avoid timeout issues Some of our builds have been timing out (over 1 hour), on AppVeyor
2016-07-05 08:50:05 +08:00
appveyor integration
2015-06-16 08:58:07 +08:00
install:
Optimize appveyor build - AppVeyor does not run matrix builds in parallel, so creating a matrix with the intent to speed up the build will actually result in longer build times, as each matrix will execute in a brand new VM. - tox does not detect 64 bit installations in AppVeyor, it always installs interpreters from C:\PythonX.Y, so there's no point to have 64bit builds - No need for the auxiliary script "install.ps1" because all python versions we are interested in are already pre-installed in AppVeyor
2015-12-11 09:48:17 +08:00
- echo Installed Pythons
- dir c:\Python*
appveyor integration
2015-06-16 08:58:07 +08:00
Only execute "coveralls" toxenv on master once Just noticed that the "coveralls" env was being execute after each env. This was introduced by mistake in #2056
2016-11-25 02:08:51 +08:00
- if "%TOXENV%" == "pypy" call scripts\install-pypy.bat
Test with pypy and enable coveralls in AppVeyor * Install pypy using chocolatey * Enable coveralls test environment in AppVeyor * Suggest maintaining build matrix in .travis.yml by using "tox --listenvs" Fix #1254
2016-01-31 06:48:15 +08:00
Use py36 as preferred Python 3 interpreter for CI testing
2017-08-15 06:28:54 +08:00
- C:\Python36\python -m pip install --upgrade --pre tox
appveyor integration
2015-06-16 08:58:07 +08:00
build: false # Not a C# project, build stuff at the test step instead.
test_script:
Only execute "coveralls" toxenv on master once Just noticed that the "coveralls" env was being execute after each env. This was introduced by mistake in #2056
2016-11-25 02:08:51 +08:00
- call scripts\call-tox.bat