[plugins] Handle multiprocess & cover together

[nicolasgrasset]

Addressing issue #820 and #710

I am relying on coverage's own method to run in parallel and store each worker's coverage in a separate .coverage file that gets combined in the report() method.

[jszakmeister]

I'm sure you tested it, but I just want to double check: does this actually produce a useful coverage report with this change? Any gotchas?

[nicolasgrasset]

Awesome @jszakmeister, yes for sure. We've been using it in our continuous integration stack for the past few weeks and it works great.

[jszakmeister]

Good to know. Thank you. I'm looking to include this in 1.4.0.

[gst]

Hi,
about this:
just to know when the 1.4.0 release is foreseen ? more or less.. if you have an idea.

[jszakmeister]

@gst Sorry, I don't have a date in mind. It really depends on how bogged down I get at work. It probably won't happen until the end of the year, or early next year. Things tend to slow down around then, and I can take some extra time off work to wrap up loose ends.

[dhirschfeld]

I tried this branch out on a large test-suite with --processes=20 and after a short while all tests fail with IOError: [Errno 232] The pipe is being closed

Python 2.7, win64

[nicolasgrasset]

I could not reproduce the issue with Python 2.7 on OSX and running with --processes=20.

Could it be that any part of your app/tests is not thread-safe?

[jszakmeister]

Thank you @fellowshipofone! Sorry it took so long to get merged.

[nicolasgrasset]

Awesome, thanks!!