[TIP] Problem collecting coverage for D-Bus activated subprocesses

[Ned Batchelder]

On 8/8/14 1:17 PM, Barry Warsaw wrote:
> I've been working on my test suite and I have gotten everything working pretty
> well.  I'm seeing coverage numbers much closer to what I expected.  Most are
> in the 90-100% range with a few modules dipping to 80% (they are not yet
> pragma'd).
>
> The last thing that's bugging me is that I have two modules that just cannot
> be omitted away.  I'm still seeing
>
> .tox/coverage/lib/python3.4/distutils/__init__
> .tox/coverage/lib/python3.4/site-packages/pkg_resources
>
> both showing up in the report, with understandably low numbers, which badly
> skews my overall coverage.  I even have this in my coverage config file:
>
> [run]
> branch = true
> parallel = true
> omit =
>       setup*
>       systemimage/data/*
>       systemimage/docs/*
>       systemimage/testing/*
>       systemimage/tests/*
>       /usr/lib/*
>      .tox/coverage/lib/python3.4/distutils/__init__
>      .tox/coverage/lib/python3.4/site-packages/pkg_resources
>
> This works for everything except those two .tox rooted paths, which always
> show up in the reports.  I've also tried adding those omits to other sections,
> but nothing seems to work.
>
> Do you have any thoughts on why those are showing up, or how to strip them
> from the results?

I would have thought those patterns would work.  Any chance there's a 
way I can reproduce your scenario?

--Ned.
>
> Cheers,
> -Barry
>
>
> _______________________________________________
> 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/20140809/290cdc99/attachment.htm>