[core-workflow] Choosing a code coverage reporter

Antoine Pitrou solipsis at pitrou.net
Wed Nov 23 06:35:46 EST 2016


On Tue, 22 Nov 2016 20:08:48 +0000
Brett Cannon <brett at python.org> wrote:
> I have both Codecov and Coveralls up and running. If you have an
> opinion/preference, please vote at
> https://github.com/brettcannon/cpython-ci-test/issues/27 using the
> reactions on the appropriate comment (.e.g +1/-1 reaction for Codecov
> and/or Coveralls). Links to the code coverage results are in the issue. If
> people want to see how they interact with PRs, feel free to look at
> https://github.com/brettcannon/cpython-ci-test/pull/32 (once the CI run is
> finished).

There are interesting oddities, such as coverage for the toplevel of
weakref.py:
https://codecov.io/gh/brettcannon/cpython-ci-test/src/065dc67d234b5550fb847b79a963d13b90002787/Lib/weakref.py

I presume weakref is being imported early in the interpreter
initialization process, when coverage hasn't been enabled yet?

Regards

Antoine.




More information about the core-workflow mailing list