Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge master into features due to recent CI updates #2060

Merged
merged 10 commits into from
Nov 14, 2016
Merged

Merge master into features due to recent CI updates #2060

merged 10 commits into from
Nov 14, 2016

Conversation

nicoddemus
Copy link
Member

No description provided.

nicoddemus and others added 10 commits November 11, 2016 19:26
Allow problematic jobs to fail instead of commenting them out
Use a wrapper script to bypass check-manifest if not under git
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).
Use one job for each tox env on AppVeyor
Docs: Added pytest promotional talk in Russian
@coveralls
Copy link

Coverage Status

Coverage remained the same at 92.682% when pulling 73d4815 on master into 6876ba9 on features.

@flub flub merged commit 7574033 into features Nov 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants