- Notifications
You must be signed in to change notification settings - Fork302
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
landscape-bot commentedDec 13, 2015
gsnedders commentedDec 13, 2015
Build failure is because coverage >= 4.0.0 doesn't support 3.2 |
gsnedders commentedDec 14, 2015
gsnedders commentedDec 15, 2015
For the curious wondering why we're going with the more obscure codecov instead of coveralls: codecov have branch coverage. |
hoppipolla-critic-bot commentedDec 16, 2015
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 donot make in-place history rewrites (e.g. via |
landscape-bot commentedDec 21, 2015
|
gsnedders commentedDec 21, 2015
PyPy with coverage seemsreally slow for some reason; should probably move to only having coverage with CPython. |
gsnedders commentedDec 21, 2015
And PyPy3k fails big-time with stuff like: |
landscape-bot commentedJan 12, 2016
|
gsnedders commentedJan 16, 2016
The PyPy3k issue is reported ashttps://bitbucket.org/pypy/pypy/issues/2225/pypy3k-settrace-_trace-messes-up-scoping FWIW |
landscape-bot commentedMar 18, 2016
gsnedders commentedMar 18, 2016
@jgraham r? |
codecov-io commentedMar 18, 2016
Current coverage is |
No description provided.