[TIP] Merging coverage results

Ned Batchelder ned at nedbatchelder.com
Sun Jun 2 04:55:53 PDT 2013

Alex, you seem to be on the cutting edge of unusual uses of 
coverage.py!  When you say you have the data in memory, what does that 
mean exactly?

It sounds like what you need is a refactoring of 
coverage/data.py:CoverageData.combine_parallel_data to allow you to feed 
data into a combining step.


On 6/1/2013 4:16 PM, Alex Gaynor wrote:
> Hi all,
> I'm looking to merge some coverage results from different CI runs, I 
> see coverage.py has a combine option which basically does what I want. 
> However, I have an interesting constraint! I don't have a disk, I just 
> have the .coverage data loaded up in memory. The format looks pretty 
> simple, so I bet I could write a merger myself, but I wonder if 
> there's a programmatic API that would do it for me? I traced through 
> the code, and it doesn't look like there's one that I could easily 
> use, but perhaps I missed something!
> Alex
> -- 
> "I disapprove of what you say, but I will defend to the death your 
> right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
> "The people's good is the highest law." -- Cicero
> GPG Key fingerprint: 125F 5C67 DFE9 4084
> _______________________________________________
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
> http://lists.idyll.org/listinfo/testing-in-python

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20130602/6f161733/attachment.htm>

More information about the testing-in-python mailing list