Opened at 2007-08-17T01:33:59Z
Last modified at 2010-02-27T18:19:40Z
#109 closed defect
our figleaf line-counting code is broken again — at Version 2
| Reported by: | warner | Owned by: | warner |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.7.0 |
| Component: | dev-infrastructure | Version: | 1.5.0 |
| Keywords: | figleaf | Cc: | |
| Launchpad Bug: |
Description (last modified by warner)
http://allmydata.org/tahoe-figleaf/figleaf-edgy-432/allmydata.util.version_class.html
This code-coverage annotation is weird. I think we've got another bug in the way that figleaf figures out which lines are which. This is the only file for which I'm seeing weird behavior, though, so maybe it is related to the fact that version_class is imported slightly weirdly: (allmydata/__init__.py imports allmydata._version which imports allmydata.util.version_class which must of course import allmydata.util.__init__ first.. ok, maybe not all that weird.
Change History (2)
comment:1 Changed at 2007-08-17T01:35:45Z by warner
comment:2 Changed at 2007-08-17T01:36:14Z by warner
- Description modified (diff)
Note: See
TracTickets for help on using
tickets.
looking at that annotated file, it's almost as if all the lines of code that were executed at initial import were then removed from the set of lines that figleaf thought got executed, like there's some sort of set math gone wrong.