Coverage Broken: why does nobody care?

Hi! I see both PR’s are merged as a part of 3.3.2. But we have same behavior on 3.3.3 (Coverage drop from 80% to 31%) and this one is just closed Draft: Fix coverage reporting with for comprehensions by vijaykramesh · Pull Request #17239 · scala/scala3 · GitHub. This is the last part of the migration. Could you please tell, is it finally fixed and which version is it?

The original issue was fixed and released in Scala 3.3.2 / 3.3.3 - see coverage changelog for Scala 3.3.3 Release 3.3.3 · scala/scala3 · GitHub
It contains both fixes mentioned in the original issue: Compiler produces incorrect/incomplete coverage data · Issue #16634 · scala/scala3 · GitHub
I guess your problems might be related to some other issues. In such a case, we’d require a reproducer to fix it.

If you’ve used exclusions for coverage reports in Scala 2, then these were added in Scala 3.3.4 (as a backport from 3.4.2)(Port coverage filter options for packages and files by KacperFKorban · Pull Request #19727 · scala/scala3 · GitHub)

2 Likes

Thank you! It wasn’t 31, it was pipeline failure (some tests were not included) and missing exclusion filters. Now looks like the reports are almost identical and I have 65 compared to 80. I’ll try to collect differences and open an issue