[core-workflow] Choosing a code coverage reporter

[Brett Cannon]

Yep, and it's a known issue. If you look at the devinabox README you will
see there are complex instructions o  how to work around it, but since they
are theoretically brittle I didn't bother setting it up.

On Wed, Nov 23, 2016, 03:36 Antoine Pitrou, <solipsis at pitrou.net> wrote:

> 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.
>
>
> _______________________________________________
> core-workflow mailing list
> core-workflow at python.org
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20161123/675da248/attachment.html>