Re: [Python-Dev] Code coverage doesn't show .py stats

2010-11-04 Thread Walter Dörwald
On 03.11.10 19:21, anatoly techtonik wrote: Hi, Python code coverage doesn't include any .py files. What happened? http://coverage.livinglogic.de/ Did it work before? It did, however currently the logfile http://coverage.livinglogic.de/testlog.txt shows the following exception:

[Python-Dev] Code coverage doesn't show .py stats

2010-11-03 Thread anatoly techtonik
Hi, Python code coverage doesn't include any .py files. What happened? http://coverage.livinglogic.de/ Did it work before? -- anatoly t. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe:

[Python-Dev] Code coverage metrics

2010-04-06 Thread anatoly techtonik
Where can I find public reports with Python tests code coverage? -- anatoly t. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe:

Re: [Python-Dev] Code coverage metrics

2010-04-06 Thread Senthil Kumaran
On Tue, Apr 06, 2010 at 12:40:35PM +0300, anatoly techtonik wrote: Where can I find public reports with Python tests code coverage? Here: http://coverage.livinglogic.de/ -- Senthil ___ Python-Dev mailing list Python-Dev@python.org

Re: [Python-Dev] Code coverage metrics

2010-04-06 Thread Antoine Pitrou
Senthil Kumaran orsenthil at gmail.com writes: On Tue, Apr 06, 2010 at 12:40:35PM +0300, anatoly techtonik wrote: Where can I find public reports with Python tests code coverage? Here: http://coverage.livinglogic.de/ The fact that the log shows some test failures isn't very comforting.

Re: [Python-Dev] Code coverage metrics

2010-04-06 Thread anatoly techtonik
On Tue, Apr 6, 2010 at 7:31 PM, Georg Brandl g.bra...@gmx.net wrote: Where can I find public reports with Python tests code coverage? Here: http://coverage.livinglogic.de/ Thank you. What is the status of getting these stats on python.org? Wouldn't status imply that there is a plan to do

Re: [Python-Dev] Code coverage metrics

2010-04-06 Thread C. Titus Brown
On Tue, Apr 06, 2010 at 10:36:14PM +0300, anatoly techtonik wrote: On Tue, Apr 6, 2010 at 7:31 PM, Georg Brandl g.bra...@gmx.net wrote: Where can I find public reports with Python tests code coverage? Here: http://coverage.livinglogic.de/ Thank you. What is the status of getting

Re: [Python-Dev] Code coverage metrics

2010-04-06 Thread Brett Cannon
On Tue, Apr 6, 2010 at 12:42, C. Titus Brown c...@msu.edu wrote: On Tue, Apr 06, 2010 at 10:36:14PM +0300, anatoly techtonik wrote: On Tue, Apr 6, 2010 at 7:31 PM, Georg Brandl g.bra...@gmx.net wrote: Where can I find public reports with Python tests code coverage? Here:

[Python-Dev] Code coverage

2008-09-19 Thread Walter Dörwald
Hello all! The code coverage site at http://coverage.livinglogic.de/ was broken for the last few months. It's fixed again now and runs the test suite once per day with regrtest.py -T -N -uurlfetch,largefile,network,decimal Servus, Walter ___

Re: [Python-Dev] Code coverage

2008-09-19 Thread Brett Cannon
On Fri, Sep 19, 2008 at 11:57 AM, Walter Dörwald [EMAIL PROTECTED] wrote: Hello all! The code coverage site at http://coverage.livinglogic.de/ was broken for the last few months. It's fixed again now and runs the test suite once per day with regrtest.py -T -N

Re: [Python-Dev] Code coverage reporting.

2006-06-21 Thread Walter Dörwald
Titus Brown wrote: On Mon, Jun 19, 2006 at 08:37:30AM -0400, Benji York wrote: - Brett Cannon wrote: - But it does seem accurate; random checking of some modules that got high - but not perfect covereage all seem to be instances where dependency - injection would be required to get the

Re: [Python-Dev] Code coverage reporting.

2006-06-19 Thread Benji York
Brett Cannon wrote: But it does seem accurate; random checking of some modules that got high but not perfect covereage all seem to be instances where dependency injection would be required to get the tests to work since they were based on platform-specific things. I don't know if we need

Re: [Python-Dev] Code coverage reporting.

2006-06-19 Thread Walter Dörwald
Benji York wrote: Brett Cannon wrote: But it does seem accurate; random checking of some modules that got high but not perfect covereage all seem to be instances where dependency injection would be required to get the tests to work since they were based on platform-specific things. I

Re: [Python-Dev] Code coverage reporting.

2006-06-19 Thread Brett Cannon
On 6/19/06, Benji York [EMAIL PROTECTED] wrote: Brett Cannon wrote: But it does seem accurate; random checking of some modules that got high but not perfect covereage all seem to be instances where dependency injection would be required to get the tests to work since they were based on

Re: [Python-Dev] Code coverage reporting.

2006-06-19 Thread Benji York
Brett Cannon wrote: Ah, do the union of the coverage! Yeah, that would be nice and give the most accurate coverage data in terms of what is actually being tested. But as Titus says in another email, question is how to get that data sent back to be correlated against. It might be

[Python-Dev] Code coverage reporting.

2006-06-18 Thread Titus Brown
Folks, I've just run a code coverage report for the python2.4 branch: http://vallista.idyll.org/~t/temp/python2.4-svn/ This report uses my figleaf code, http://darcs.idyll.org/~t/projects/figleaf-latest.tar.gz I'm interested in feedback on a few things -- * what more would

Re: [Python-Dev] Code coverage reporting.

2006-06-18 Thread Brett Cannon
On 6/15/06, Titus Brown [EMAIL PROTECTED] wrote: Folks,I've just run a code coverage report for the python2.4 branch:http://vallista.idyll.org/~t/temp/python2.4-svn/This report uses my figleaf code, http://darcs.idyll.org/~t/projects/figleaf-latest.tar.gzVery nice, Titus! I'm interested in

Re: [Python-Dev] Code coverage reporting.

2006-06-18 Thread Nick Coghlan
Brett Cannon wrote: But it does seem accurate; random checking of some modules that got high but not perfect covereage all seem to be instances where dependency injection would be required to get the tests to work since they were based on platform-specific things. There's something odd