-
Notifications
You must be signed in to change notification settings - Fork 294
Add code coverage reports #220
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
Conversation
Build failure is because coverage >= 4.0.0 doesn't support 3.2 |
For the curious wondering why we're going with the more obscure codecov instead of coveralls: codecov have branch coverage. |
Critic review: https://critic.hoppipolla.co.uk/r/6052 This is an external review system which you may optionally use for the code review of your pull request. In order to help critic track your changes, please do not make in-place history rewrites (e.g. via |
|
PyPy with coverage seems really slow for some reason; should probably move to only having coverage with CPython. |
And PyPy3k fails big-time with stuff like:
|
|
The PyPy3k issue is reported as https://bitbucket.org/pypy/pypy/issues/2225/pypy3k-settrace-_trace-messes-up-scoping FWIW |
@jgraham r? |
Current coverage is
|
No description provided.