Repository navigation
trace misreports "missing" lines #54145
Description
| BPO | 9936 |
|---|---|
| Nosy | @terryjreedy, @abalkin |
| Files |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = 'https://github.com/abalkin'
closed_at = <Date 2010-10-05.16:51:11.286>
created_at = <Date 2010-09-24.02:55:53.777>
labels = ['type-bug', 'library']
title = 'trace misreports "missing" lines'
updated_at = <Date 2010-10-05.16:51:11.285>
user = 'https://github.com/abalkin'bugs.python.org fields:
activity = <Date 2010-10-05.16:51:11.285>
actor = 'belopolsky'
assignee = 'belopolsky'
closed = True
closed_date = <Date 2010-10-05.16:51:11.286>
closer = 'belopolsky'
components = ['Library (Lib)']
creation = <Date 2010-09-24.02:55:53.777>
creator = 'belopolsky'
dependencies = []
files = ['18990', '18991', '18998']
hgrepos = []
issue_num = 9936
keywords = ['patch']
message_count = 5.0
messages = ['117257', '117258', '117321', '117430', '117431']
nosy_count = 4.0
nosy_names = ['terry.reedy', 'belopolsky', 'Arfrever', 'eli.bendersky']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue9936'
versions = ['Python 3.1', 'Python 2.7', 'Python 3.2']
Activity
abalkin commentedon Sep 24, 2010
With the attached traceme.py,
$ python -m trace -m -s -c traceme.py lines cov% module (path) 2 50% traceme (traceme.py) $ cat traceme.cover x = (1, >>>>>> 2, 1: 3)This is wrong because all lines in traceme.py are executed.
abalkin commentedon Sep 24, 2010
I am attaching a patch that fixes this issue. Need to add a unit test.
abalkin commentedon Sep 24, 2010
Fixed in r84994, r84995 (3.1) and r84996 (2.7).
Arfrever commentedon Sep 26, 2010
test_issue9936 fails on 2.7 branch.
See e.g. http://www.python.org/dev/buildbot/2.7.stable/builders/sparc%20solaris10%20gcc%202.7/builds/268/steps/test/logs/stdio
abalkin commentedon Sep 26, 2010
On Sun, Sep 26, 2010 at 5:47 PM, Arfrever Frehtes Taifersar Arahesis
<[email protected]> wrote:
..
Should be fixed by r85020. Thanks.