search

pytest-dev / py

Python development support library (note: maintenance only)
MIT License
67 stars 106 forks source link

Travis: use Ubuntu Xenial, pypy3, coverage #208

Closed blueyed closed 5 years ago

blueyed commented 5 years ago

@nicoddemus Do you feel like adding coverage reporting to codecov for AppVeyor? (should use a windows flag then probably, but I skipped using flags for now - this appears to trigger timeouts on codecov still)

blueyed commented 5 years ago

Coverage can be seen at https://codecov.io/gh/pytest-dev/py/tree/a54d2d325b0f63fa244a0096af574a0f0c255295.

nicoddemus commented 5 years ago

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?

blueyed commented 5 years ago

Yes, codecov can be annoying (mostly the connection timeouts, but this might be caused by using (many) flags after all). No idea really about the coverage changes being off - this might also be the reporting itself (coveragepy), or some misconfiguration on our side (pytest repo).

I've started investigating other providers, but in general (if it is working) codecov is still one of the best.

blueyed commented 5 years ago

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).

blueyed commented 5 years ago

Primarily I wanted to get CI going again here.