[Python-Dev] C code coverage report with lcov (original) (raw)

R. David Murray rdmurray at bitdance.com
Mon Jul 29 20:11:17 CEST 2013

On Mon, 29 Jul 2013 13:58:55 -0400, Brett Cannon <brett at python.org> wrote:

On Mon, Jul 29, 2013 at 1:15 PM, Christian Heimes <christian at python.org>wrote:

> Hi, > > I have done some experiments with GCC's gcov and lcov to get the C code > coverage of our unit test suite. You may find today's report at > > http://tiran.bitbucket.org/python-lcov/

Thanks! I took a quick poke around and it seems some things are legitimately not being executed, while others are error conditions that we wouldn't expect to occur (e.g. memory exhaustion). If we ever decide to get serious about code coverage (both C and Python code) we may need to have a discussion as a group about our feelings related to pragmas dictating when code should be left out of coverage reports.

I suspect Victor will eventually have something for us for exercising the memory exhaustion code :)

--David

More information about the Python-Dev mailing list