Re: [Python-Dev] C code coverage report with lcov

2013-07-31 Thread Brett Cannon
On Tue, Jul 30, 2013 at 8:28 PM, Christian Heimes wrote: > Am 29.07.2013 21:48, schrieb Antoine Pitrou: > > Ideally, we should run coverage runs on different systems (Unices, > > Windows...) and merge the results together, so that we know which paths > > are really uncovered. > > I don't that is e

Re: [Python-Dev] C code coverage report with lcov

2013-07-30 Thread Christian Heimes
Am 29.07.2013 21:48, schrieb Antoine Pitrou: > Ideally, we should run coverage runs on different systems (Unices, > Windows...) and merge the results together, so that we know which paths > are really uncovered. I don't that is easily possible. The coverage report depends on GCC and its gcov exten

Re: [Python-Dev] C code coverage report with lcov

2013-07-30 Thread Christian Heimes
Am 29.07.2013 19:15, schrieb Christian Heimes: > 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/ > > I'm working on a patch for our Makefile to include

Re: [Python-Dev] C code coverage report with lcov

2013-07-29 Thread Christian Heimes
Am 29.07.2013 21:38, schrieb Brett Cannon: > If there's a way to report just function coverage then I think > that's a great place to start. lcov's genhtml command doesn't support just function coverage. But I have removed branch coverage. It makes the report a little bit more readable. Christian

Re: [Python-Dev] C code coverage report with lcov

2013-07-29 Thread Antoine Pitrou
On Mon, 29 Jul 2013 21:31:02 +0200 Christian Heimes wrote: > Am 29.07.2013 19:58, schrieb Brett Cannon: > > 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).

Re: [Python-Dev] C code coverage report with lcov

2013-07-29 Thread Brett Cannon
On Mon, Jul 29, 2013 at 3:31 PM, Christian Heimes wrote: > Am 29.07.2013 19:58, schrieb Brett Cannon: > > 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

Re: [Python-Dev] C code coverage report with lcov

2013-07-29 Thread Christian Heimes
Am 29.07.2013 19:58, schrieb Brett Cannon: > 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 P

Re: [Python-Dev] C code coverage report with lcov

2013-07-29 Thread R. David Murray
On Mon, 29 Jul 2013 13:58:55 -0400, Brett Cannon wrote: > On Mon, Jul 29, 2013 at 1:15 PM, Christian Heimes 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.b

Re: [Python-Dev] C code coverage report with lcov

2013-07-29 Thread Brett Cannon
On Mon, Jul 29, 2013 at 1:15 PM, Christian Heimes 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 se

[Python-Dev] C code coverage report with lcov

2013-07-29 Thread Christian Heimes
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/ I'm working on a patch for our Makefile to include all steps in one simple make tag. http://bugs.python.org/issue1