Travis: use Ubuntu Xenial, pypy3, coverage #208
Conversation
Hopefully helps with py2 failure: https://travis-ci.org/pytest-dev/py/jobs/492914885
|
@nicoddemus |
blueyed
changed the title
|
Coverage can be seen at https://codecov.io/gh/pytest-dev/py/tree/a54d2d325b0f63fa244a0096af574a0f0c255295. |
|
TBH I'm not entirely happy with codecov in general, we have been having frequent problems with it: connection resets during builds causing them to fail (albeit in the last week or so I have not seen those anymore), and coverage changes that we could not explain (doc only changes making coverage drop for example). What is your opinion? |
|
Yes, codecov can be annoying (mostly the connection timeouts, but this might be caused by using (many) flags after all). I've started investigating other providers, but in general (if it is working) codecov is still one of the best. |
|
We can leave coverage out of this PR for now, but I've figured that it would be helpful with checking if we miss something (I've started to add support / fixes for newer pytest). |
|
Primarily I wanted to get CI going again here. |
| #- DEPS="pytest~=3.1.0" | ||
| - DEPS="pytest~=2.9.0" | ||
| - DEPS="pytest~=3.0.0" | ||
| #- DEPS="pytest~=3.1.0" |
There was a problem hiding this comment.
Before already, just indented.
Would be changed in the next step, e.g. by testing against pytest 4.2.
There was a problem hiding this comment.
Oops did not notice that, sorry
| - '3.4' | ||
| - '3.5' | ||
| - '3.6' | ||
| # - 'pypy2.7-6.0' |
There was a problem hiding this comment.
Since pypy is failing anyway, I've only kept pypy3 (previously it was only pypy).
No description provided.