Re: [Python-Dev] Code coverage doesn't show .py stats
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: Traceback (most recent call last): File Lib/test/regrtest.py, line 1500, in module main() File Lib/test/regrtest.py, line 696, in main r.write_results(show_missing=True, summary=True, coverdir=coverdir) File /home/coverage/python/Lib/trace.py, line 319, in write_results lnotab, count) File /home/coverage/python/Lib/trace.py, line 369, in write_results_file outfile.write(line.expandtabs(8)) UnicodeEncodeError: 'ascii' codec can't encode character '\xe4' in position 30: ordinal not in range(128) BTW, this is the py3k branch (i.e. http://svn.python.org/snapshots/python3k.tar.bz2) It seems the trace module has a problem with unicode. Servus, Walter ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Code coverage metrics
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 http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Code coverage metrics
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. Regards Antoine. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Code coverage metrics
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 so? It is not that hard to create that plan given that there is a fair amount of developers who care about code coverage. -- anatoly t. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Code coverage metrics
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 these stats on python.org? Wouldn't status imply that there is a plan to do so? It is not that hard to create that plan given that there is a fair amount of developers who care about code coverage. Anatoly, nonetheless, I don't know of any plan :). I keep on shaving yaks when trying to get test coverage posted somewhere; it's actually not a trivial problem to set it up automatically and reliably, in my experience. If you are interested in volunteering to help, I'm sure it would be appreciated -- I suspect the right place to start would be get test coverage running reproducibly and reliably on your own machines and posted somewhere; then you could ask for permissions to post it somewhere on *.python.org. (I don't see why we care where it's posted, but that's what you asked about.) I keep on running into technical barriers in getting cross-platform code coverage analysis working, which would be quite valuable; it's easy to get it working once, but to keep it working is a maintenance task that involves regular effort, again, in my experience. best, --titus -- C. Titus Brown, c...@msu.edu ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Code coverage metrics
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: 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 so? It is not that hard to create that plan given that there is a fair amount of developers who care about code coverage. Anatoly, nonetheless, I don't know of any plan :). I keep on shaving yaks when trying to get test coverage posted somewhere; it's actually not a trivial problem to set it up automatically and reliably, in my experience. If you are interested in volunteering to help, I'm sure it would be appreciated -- I suspect the right place to start would be get test coverage running reproducibly and reliably on your own machines and posted somewhere; then you could ask for permissions to post it somewhere on *.python.org. (I don't see why we care where it's posted, but that's what you asked about.) I keep on running into technical barriers in getting cross-platform code coverage analysis working, which would be quite valuable; it's easy to get it working once, but to keep it working is a maintenance task that involves regular effort, again, in my experience. And just in general, it requires someone stepping forward to do it. While there might be several developers who find test coverage important (me included), it's a matter of taking the time to set up something that will work. For me personally that is more time than I have for my volunteer work for Python as I have other things that I put at a higher priority. It's an overused, worn out statement, but it's open source so stuff only gets done when someone REALLY has the desire and time to do something. I'm grateful that Walter has done what he has. If someone steps forward to write up instructions on how to run figleaf or coverage.py over the test suite then that would be appreciated. But just because something isn't technically hard, doesn't mean it isn't hard from the perspective of time and motivation. -Brett ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Code coverage
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 -uurlfetch,largefile,network,decimal Thanks, Walter! Hopefully once Benjamin's testing cleanup lands we work on improving our test coverage. -Brett ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Code coverage reporting.
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 tests to work since they were - based on platform-specific things. - - I don't know if we need it hooked into the buildbots (unless it is dirt - cheap to generate the report). - - It would be interesting to combine the coverage over several platforms - and report that. Yes, I noticed that the platform specific stuff doesn't get covered, of course. It's very easy to do, *if* there's any way to get the coverage database from a central location (or send it back to a central location). It might be interesting to run coverage analysis -- either figleaf or Ned Batchelder's module[0] -- once a week on select buildbot machines (one linux, one windows, one mac, or some such) and make the coverage databases available via something like a downloadable static file. Then anyone could download those files and do Interesting Things with them. --titus [0] I'm sorry, I don't know how Walter Dorwald generates his coverage; if it's OSS, then it'd be better to use because it shows C code coverage as well. The script at http://styx.livinglogic.de/~walter/python/coverage/PythonCodeCoverage.py definitely is open source, so feel free to use in any way you want. The web application front end though isn't open source. The SQL script to recreate the database can be found here: http://styx.livinglogic.de/~walter/python/coverage/coverage.sql Servus, Walter ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Code coverage reporting.
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 it hooked into the buildbots (unless it is dirt cheap to generate the report). It would be interesting to combine the coverage over several platforms and report that. -- Benji York ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Code coverage reporting.
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 don't know if we need it hooked into the buildbots (unless it is dirt cheap to generate the report). It would be interesting to combine the coverage over several platforms and report that. The code coverage report should include how often a line got executed, not just if it got executed at all. This makes it possible to se hotspots in the code. BTW, if there's interest, I can change the code behind http://coverage.livinglogic.de so that instead of importing the data into a database, static HTML files are created, so that we can run the job more often on one of the Python servers. Currently the job runs once a month with ./python Lib/test/regrtest.py -T -N -R :: -uurlfetch,largefile,network,decimal and takes about one hour to run the tests. The source code is available from http://styx.livinglogic.de/~walter/python/coverage/PythonCodeCoverage.py Servus, Walter ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Code coverage reporting.
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 platform-specific things. I don't know if we need it hooked into the buildbots (unless it is dirt cheap to generate the report).It would be interesting to combine the coverage over several platforms and report that.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. -Brett ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Code coverage reporting.
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 interesting as a BuilBot extension: you already know the definitive identity of the thing that you're running (svn path and revision), a central server with established communication channel, plus all the other BuildBot machinery. -- Benji York ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Code coverage reporting.
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 feedback on a few things -- * what more would you want to see in this report? * is there anything obviously wrong about the report?In other words... comments solicited ;). Making the comments in the code stand out less (i.e., not black) might be handy since my eye still gets drawn to the comments a lot.It would also be nice to be able to sort on different things, such as filename. 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. By the by, I'm also planning to integrate this into buildbot on someprojects.I'll post the scripts when I get there, and I'd be happy to help Python itself set it up, of course.I don't know if we need it hooked into the buildbots (unless it is dirt cheap to generate the report). But hooking it up to the script in Misc/build.sh that Neal has running to report reference leaks and fundamental test failures would be wonderful. -Brett ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Code coverage reporting.
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 going on with __future__.py, though. The module level code all shows up as not executed, but the bodies of the two _Feature methods both show up as being run. I'm curious as to how a function body can be executed without executing the function definition first :) As far as making the comments/docstrings less obvious goes, grey is usually a good option for that. Cheers, Nick. -- Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia --- http://www.boredomandlaziness.org ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
