[TIP] confusing coverage message

Chris Withers chris at simplistix.co.uk
Tue Jan 29 10:19:35 PST 2013


On 29/01/2013 13:06, Chris Withers wrote:
> On 29/01/2013 12:54, Ned Batchelder wrote:
>> I can explain that message. It means, bug #92 still hasn't been fixed:
>> https://bitbucket.org/ned/coveragepy/issue/92/finally-clauses-arent-treated-properly-in
>>
>> :(
>>
>> It is at the top of my TODO list, but might be difficult... In the
>> meantime, you can add a pragma comment ("#pragma: no branch") to quiet
>> it if you need to.

Hmm, this one looks like a real bug:

http://jenkins.simplistix.co.uk/job/checker-buildout/PYTHON=2.7,label=linux/75/coveragepy/checker_checkers_jenkins.html

I wouldn't expect line 40 to *ever* jump to line 70 there...

Chris

-- 
Simplistix - Content Management, Batch Processing & Python Consulting
             - http://www.simplistix.co.uk



More information about the testing-in-python mailing list