Open andreisilviudragnea opened 2 years ago
@ckipp01 Is there anyone checking bug reports? This seems like a major bug to me, which affects both V1 and V2.
Hey @andreisilviudragnea, at the moment I'm not actively working on scoverage. The attempt to add Scala 3 support and getting the V2 out was all being done on my free time, and it was taking a pretty large chunk of it that I'd prefer to be used on the other projects I have. However I do still plan to cut releases for new Scala versions and address anything that requires an immediate response.
Potentially over break I'll get back to some of this and try to wrap it all up, look into some of the issue reports, etc, but no promises.
@ckipp01 Is there an active maintainer for scoverage?
I am asking because my team is checking Scala community support for the dependencies in our project, since lack of support affects our usage of Scala language in the future.
@ckipp01 Is there an active maintainer for scoverage?
At the moment I'm really the only one.
There are cases when coverage is mistakenly reported as 100%, even if it is not true:
Running
sbt coverage test coverageReport
does not fail as it should, but reports 100% coverage. I have reproduced the bug here: https://github.com/andreisilviudragnea/scoverage-bugs