Use one job for each tox env on AppVeyor #2056
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nicoddemus
force-pushed
the
appveyor-list
branch
from
e951d2e to
98fbd2c
Compare
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).
nicoddemus
force-pushed
the
appveyor-list
branch
from
98fbd2c to
f99957c
Compare
|
plese add a match for the script to manifest.in |
nicoddemus
force-pushed
the
appveyor-list
branch
from
f99957c to
ec69514
Compare
Yep, my bad. Apparently |
nicoddemus
added a commit
to nicoddemus/pytest
that referenced
this pull request
Nov 24, 2016
Just noticed that the "coveralls" env was being execute after each env. This was introduced by mistake in pytest-dev#2056
nicoddemus
added a commit
to nicoddemus/pytest
that referenced
this pull request
Nov 24, 2016
Just noticed that the "coveralls" env was being execute after each env. This was introduced by mistake in pytest-dev#2056
nicoddemus
added a commit
to nicoddemus/pytest
that referenced
this pull request
Nov 24, 2016
Just noticed that the "coveralls" env was being execute after each env. This was introduced by mistake in pytest-dev#2056
nicoddemus
added a commit
to nicoddemus/pytest
that referenced
this pull request
Nov 24, 2016
Just noticed that the "coveralls" env was being execute after each env. This was introduced by mistake in pytest-dev#2056
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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).