Unreliability of coverage when running tests in parallel

[finwe]

Coverage returns nonsenses when the test suite was ran parallel

If unable to fix, mention this behaviour in documentation and/or when running tests in parallel with coverage enabled.

[dg]

It should work, because Collector::save() uses file lock. Hmmm…

[milo]

@finwe This may happen when you run coverage-report with old coverage.dat. Are you sure it is actual one?

[finwe]

Fresh, running tester and coverage right one after another.

[milo]

@finwe And without parallel run it is ok?

[finwe]

Yes.

On 26. února 2014 22:44:05 CET, "Miloslav Hůla" notifications@github.com wrote:

@finwe And without parallel run it is ok?

---

Reply to this email directly or view it on GitHub:
#103 (comment)

Posláno z kapsy. Omluvte, prosím, mou stručnost.

[milo]

@finwe Could you try to completely delete the coverage.dat? I seems to be not due to parallel run but due to already coverage.dat (from last run) existence with some data.

[finwe]

I actually do that in my coverage shell script every time after generating coverage, as not deleting it caused same kind of errors (IIRC even when not running tests in parallel).

[milo]

@finwe In that case I cannot reproduce it. Is your code publicly available? I could try it directly.

[finwe]

finwe/php-cs-fix@1d881c94b84592a70f4e9e5f2b515bec02bd62af

[milo]

@finwe Still cannot reproduce it. Can you still reproduce it?

[finwe]

Oh my god, it is alright now. And I reproduced it thrice behore submitting the issue. I'll reopen should I experience it again.