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

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).
This commit is contained in:
Bruno Oliveira 2016-11-12 11:50:22 -02:00
parent 5185f2a6ae
commit c169c883d3
1 changed files with 16 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
appveyor.yml
View File

@ -6,17 +6,23 @@ environment:
# https://www.appveyor.com/docs/build-configuration#secure-variables # https://www.appveyor.com/docs/build-configuration#secure-variables
matrix: matrix:
# create multiple jobs to execute a set of tox runs on each; this is to workaround having - TOXENV: "linting"
# builds timing out in AppVeyor - TOXENV: "py26"
- TOXENV: "linting,py26,py27,py33,py34,py35" - TOXENV: "py27"
- TOXENV: "py27-pexpect,py27-xdist,py27-trial,py35-pexpect,py35-xdist,py35-trial" - TOXENV: "py33"
- TOXENV: "py27-nobyte,doctesting,freeze,docs" - TOXENV: "py34"
- TOXENV: "py35"
- TOXENV: "pypy" - TOXENV: "pypy"
- TOXENV: "py27-pexpect"
matrix: - TOXENV: "py27-xdist"
allow_failures: - TOXENV: "py27-trial"
# pypy is disabled until #1963 gets fixed - TOXENV: "py35-pexpect"
- TOXENV: "pypy" - TOXENV: "py35-xdist"
- TOXENV: "py35-trial"
- TOXENV: "py27-nobyte"
- TOXENV: "doctesting"
- TOXENV: "freeze"
- TOXENV: "docs"
install: install:
- echo Installed Pythons - echo Installed Pythons