James Kessler

Hi, @AbdealiLoKo. Thanks for the detailed description and the link. Always helpful. 🙏 One more thing that will help though is a link to the source file that's showing this...

@AbdealiLoKo thanks for the updates. Apologies for the delay. As we discussed in email, since you have a paid subscription, you can get support by directly emailing [email protected], or by...

Also wanting to reply in full here to cover any gaps:   > I was apprehensive that I could create a MRE. But I was able to reproduce the issue...

Just didn't want to leave this un-replied to: > I seem to be seeing this more and more Another place where a assignment statement is saying there is a branch...

@AbdealiLoKo I just wanted to summarize the above, since it represents a lot of reading, which I'm sorry for, but I hope addresses all the details you shared in the...

> Antipattern 2: This one doesn't seem like a rather common pattern. Understood. I am basically thinking of any scenario where someone in parallelizing test runs for performance (such as...

@AbdealiLoKo I wanted to circle back to this issue, even though it was closed, by me, after making the best practice recommendations above. I have since discovered more about the...

@AbdealiLoKo regarding this attempt: > I went with Option 1. > > Did not solve the issue: > > Coveralls build: https://coveralls.io/jobs/133885565/source_files/19184053316 [...] I see that Coverage Reporter processed two...

Regarding your second attempt: > I tried option 2 now. And it seems like with cobertura that issue does not exist anymore. > > - Github commit - https://github.com/AbdealiLoKo/coveralls-issue/commit/7418695304da0eea30fa96337e4809642c3b6be8 >...

Hi @dbendy. Can you please share the Coveralls URL for one of your builds (or 2-build sequences) for which this occurred? If you project is private, feel free to email...