74366426b9
Travis: use last TOXENV for PATH
2018-11-11 22:08:45 +01:00
9628242423
CI: doctesting uses coverage, fiy py37 on AppVeyor
2018-11-11 21:49:59 +01:00
7b833ce5f9
Merge pull request #4368 from blueyed/toxenv-coverage
...
Travis: use coverage from existing tox env [skip appveyor]
2018-11-11 11:57:20 -02:00
dc9ceda5d2
Travis: use Xenial by default [skip appveyor]
2018-11-11 01:02:06 +01:00
825085f699
Travis: use coverage from existing tox env [skip appveyor]
2018-11-11 00:59:46 +01:00
bb8a8495ff
Revert "Attempt to fix macosx build setup"
...
This reverts commit 28dbffdaf2https://travis-ci.org/pytest-dev/pytest/jobs/452598885#L906
[skip appveyor]
2018-11-09 00:33:52 +01:00
28dbffdaf2
Attempt to fix macosx build setup
...
This has been failing as of 2018-10-23 while installing gcc with
this message:
==> Installing numpy dependency: gcc
==> Downloading https://homebrew.bintray.com/bottles/gcc-8.2.0.high_sierra.bottl
######################################################################## 100.0%
==> Pouring gcc-8.2.0.high_sierra.bottle.1.tar.gz
Error: The `brew link` step did not complete successfully
The formula built, but is not symlinked into /usr/local
Could not symlink include/c++
Target /usr/local/include/c++
already exists. You may want to remove it:
rm '/usr/local/include/c++'
To force the link and overwrite all conflicting files:
brew link --overwrite gcc
To list all files that would be deleted:
brew link --overwrite --dry-run gcc
Possible conflicting files are:
/usr/local/include/c++ -> /usr/local/Caskroom/oclint/0.13.1,17.4.0/oclint-0.13.1/include/c++
2018-10-24 12:46:45 -03:00
12f94b81c0
No longer upload code coverage to coveralls
...
We have since moved to codecov and uploading to coveralls is breaking
OS-X builds for py37 [1], so we might as well take this opportunity to drop
it.
[1] https://travis-ci.org/pytest-dev/pytest/jobs/442858038
2018-10-17 18:18:08 -03:00
6d0667f1db
CI: run specialized factors in a single job
...
Given the setup time for jobs, it makes sense to run
*-pexpect,*-trial,*-numpy in a single build job.
2018-10-14 14:27:34 +02:00
2dc619cbf4
Run docs, doctesting and linting in the same environment to save some CI time
2018-10-12 13:35:27 -03:00
28c9cc7321
coverage: use modules for source
...
This should increase coverage for subprocesses, where previously
`source` paths were used only from the config file, but not the initial
`--source` argument.
2018-09-19 07:46:19 +02:00
739f9a4a4b
Travis: use codecov-bash
...
Faster to install and will retry uploads on connection errors.
2018-09-17 14:44:47 +02:00
7537e94ddf
tests: use unittest.mock with py34+
...
Fixes https://github.com/pytest-dev/pytest/issues/3965 .
Has to work around https://github.com/tox-dev/tox/issues/706 .
No coverage for pluggymaster builds is OK though anyway.
2018-09-12 23:21:47 +02:00
9ee8d72fd2
Disable coverage during deployment stage
...
Otherwise it will fail as there's no coverage data to combine/publish
2018-09-06 09:18:47 -03:00
ec6fca4aa7
Add codecov support to AppVeyor and remove coveralls
2018-09-05 19:50:06 -03:00
f0e852b4db
Merge pull request #2800 from blueyed/coverage
...
Travis: report coverage with all builds
2018-08-30 19:41:22 -03:00
3ca70692de
Skip the "test" stage when making a release
...
Given that our guidelines demand that the CI have already passed, it seems
wasteful to run all those jobs again for the exact same commit.
As discussed in https://github.com/pytest-dev/pytest/pull/3906#issuecomment-417094481 ,
this will skip the "test" stage when building a tag for deployment.
2018-08-29 17:54:58 -03:00
417516c378
squash! Travis: report coverage with all builds
...
doctesting: remove changedir
With coverage 5 we could use COVERAGE_RCFILE to make it find the
.coveragerc, or we could add `--rcfile` to _PYTEST_TOX_COVERAGE_RUN, but
I've thought that this should not be the job that has to test if
`--pyargs` actually works.
2018-08-29 22:53:20 +02:00
f730291e67
Travis: report coverage with all builds
...
- Skips pypy for coverage, reports only py37 to coveralls
- tox: allow for TOXENV=py37-coverage
- tracks coverage in subprocesses, using coverage-enable-subprocess, and
parallel=1
- removes usedevelop with doctesting to match `--source` being used with
coverage
- keep coveralls for now, used with AppVeyor
2018-08-29 22:30:28 +02:00
16f452ef98
Merge pull request #3894 from blueyed/baseline
...
Travis: add baseline stage
2018-08-28 22:19:08 +02:00
32575f92c9
set TOXENV in test-macos template otherwise it will inherit "coveralls"
2018-08-27 20:07:51 -03:00
a260e58020
Drop 3.6 from OS-X to reduce build time
2018-08-27 20:03:12 -03:00
b2f7e02a02
Reorganize osx environments to avoid repetition as suggested in review
2018-08-27 20:02:16 -03:00
cdc72bf5a3
Travis: add baseline stage
...
Fixes https://github.com/pytest-dev/pytest/issues/3876 .
2018-08-27 23:46:24 +02:00
f786335dbb
travis: run tests on macOS
...
closes #3892
2018-08-27 17:22:27 +02:00
415fcb912b
Travis: use TOXENV=linting for linting stage
...
This will run it with `--show-diff-on-failure` then, and helps to keep
it in line / in a central place.
2018-08-25 23:14:09 +02:00
2c09930b6d
Use proper quotes for python 3.7 on travis.yml
2018-07-30 20:13:17 +00:00
c480223e88
Test with Python 3.7 on Travis and AppVeyor
2018-07-29 21:14:38 -03:00
49e82a4be8
Skip deploy stage entirely unless we have a tag
...
Borrowed from https://github.com/tox-dev/tox/pull/877
2018-07-07 12:12:07 -03:00
130100bba1
Fix reference to py36-freeze in travis and appveyor
...
Travis and AppVeyor were executing "py35-freeze", which does not actually
exist in tox.ini.
2018-06-20 07:53:41 -03:00
130f76f66e
enable pip/pre-commit caching on travis and appveyor
2018-05-27 13:05:10 +02:00
5a6a580765
clean env for the linting stage
2018-05-24 14:18:34 +02:00
df17bb2bd3
switch linting tox env to use pre-commit, clean out travis linting env as unneeded
2018-05-24 14:17:09 +02:00
6eb7af5a4e
experimentally add pre-commit for linting in travis
2018-05-24 13:51:15 +02:00
bfe2cbe875
Implement publishing to PyPI by pushing a tag
...
Fix #3060
2018-02-17 10:13:25 -02:00
e289c60c3a
Support py37 officially
...
Python 3.7.0b1 has been released:
https://www.python.org/downloads/release/python-370b1/
Fix #3168
2018-02-02 17:15:16 -02:00
73ff53c742
remove eol python from the ci config
2017-10-09 16:36:41 +02:00
a2da5a691a
Update tox and appveyor environments to use py36 by default
2017-09-18 21:38:15 -03:00
d01f08e96f
Merge branch 'features' into pluggy-master
2017-09-06 13:13:35 -03:00
11ec6aeafb
Add test environment using pluggy from master branch
...
Fix #2737
2017-09-01 18:33:30 -03:00
7b5d26c1a8
Use py36 as preferred Python 3 interpreter for CI testing
2017-08-14 20:27:28 -03:00
362b1b3c4f
Use tox release candidates in CI
...
Fix #2683
2017-08-14 19:19:20 -03:00
d5bb2004f9
Fix travis build after change from "precise" to "trusty"
...
Travis recently has changed its dist from "precise" to "trusty", so
some Python versions are no longer installed by default
2017-07-23 00:50:28 -03:00
d6000e5ab1
Remove py36 from .travis.yml
...
I thought the file was just out of date, but adding py36 made Travis
complain "InterpreterNotFound: python3.6", so I guess it was correct as
it was.
2017-06-15 20:34:36 -07:00
5d2496862a
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-15 18:46:58 -07:00
6e2bbe88b1
Test against py36 official release for consistency with other python versions
2017-04-13 17:54:56 -03:00
b61dcded37
Allow py37-nightly to fail on Travis
...
Related to #2285
2017-03-04 07:17:39 -03:00
5fd010c4c3
Simplify travis.yml with tox environment variables
2017-02-19 09:02:35 -08:00
902fd2ff6a
Add py37-nightly to travis
2017-01-22 17:20:15 -07:00
2574da8d32
Fix pytester internal plugin to work correctly with latest versions of zope.interface
...
Fix #1989
2017-01-19 20:53:35 -02:00
Daniel Hahler
Bruno Oliveira
Daniel Hahler
Jiri Kuncar
Ronny Pfannschmidt
Kale Kundert
Bruno Oliveira
Anthony Sottile
Victor Uriarte