You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure whether this is a bug or a feature... But I feel like it's a bug.
I have a SBT-project in the being, which currently has just one submodule. But it will have more the in the future, so that's why I figured multi-project setup would be appropriate.
Running sbt coverageAggregate gives the following output:
[info] Aggregating coverage from subprojects...
[info] Found 1 subproject report files [<project dir>/<submodule dir>/target/scala-2.11/scoverage-report/scoverage.xml]
[info] No subproject data to aggregate, skipping reports
It makes sense, since CoverageAggregator#aggregate explicitly checks to see if more than one file has been found.
I'd expect that aggregation of results also works if exactly one file would've been found.
If this is indeed a bug, let me know, I think I can contribute a simple PR for this 😃.
The text was updated successfully, but these errors were encountered:
So, I ran into this, and it seems to be a bug to me. I had 2 sub projects, but just one with a actual test suite, and I couldnt send my reports to coverall because coverall only gets the reports from the base project, so I had to create a fake test in my sub project just make this work.
If only one scoverage.xml file is found, the aggregator refuses to produce output:
[info] Found 1 subproject report files [/Users/arkadiy/mine/L-SPACE/l_space/target/scala-2.11/scoverage-report/scoverage.xml]
[info] No subproject data to aggregate, skipping reports
This allows aggregation of a single file
Fixesscoverage#144
Not sure whether this is a bug or a feature... But I feel like it's a bug.
I have a SBT-project in the being, which currently has just one submodule. But it will have more the in the future, so that's why I figured multi-project setup would be appropriate.
Running
sbt coverageAggregate
gives the following output:It makes sense, since
CoverageAggregator#aggregate
explicitly checks to see if more than one file has been found.I'd expect that aggregation of results also works if exactly one file would've been found.
If this is indeed a bug, let me know, I think I can contribute a simple PR for this 😃.
The text was updated successfully, but these errors were encountered: