On Mon, Feb 13, 2017 at 1:11 PM, Brett Cannon <br...@python.org> wrote: > > > On Mon, 13 Feb 2017 at 07:26 Victor Stinner <victor.stin...@gmail.com> > wrote: >> >> 2017-02-13 16:04 GMT+01:00 Donald Stufft <don...@stufft.io>: >> > I’ve also never see the random -0.01% >> > coverage of code in another project, and my guess is that there is some >> > sort >> > of non-determinism in the CPython test suite that would be a good idea >> > to >> > make deterministic anyways. >> >> Can we hide/disable Codecov notifications until this issue is fixed? >> Example of false alarm: >> https://github.com/python/cpython/pull/61#issuecomment-279291824 >> heapq.py coverage -0.77% on a change modifying Doc/library/typing.rst >> >> See also: "Adjust coverage failure threshold" >> https://github.com/python/core-workflow/issues/21 > > > Codecov's configuration is controlled by > https://github.com/python/cpython/blob/master/.codecov.yml so you can submit > a PR to propose changes to how coverage is reported. Docs can be found at > https://docs.codecov.io/docs/codecov-yaml .
Berker has https://github.com/python/cpython/pull/71 up right now. I think it looks ok so far from what I understand. _______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
