Closed duesee closed 2 weeks ago
I have now run a debug test build archiving the generated coverage report from the runner to be downloaded for inspection.
As is seems, the issue is not related to Coveralls but happens when generating the report on the runner:
... and yes, when disabling the GitHub build cache, the issue is resolved. So disabling the cache (at least for the coverage job) seems to be one way to go.
I will continue to investigate this a bit further, maybe there is a better way to fix this ...
Clearing target/debug/*
resolves the issue as well, so it seems like some build artifacts confuses the coverage data collection. Unfortunately, I was not able to pinpoint which specific build artifact causes this.
However, as opposed to disabling the GitHub cache all together, this at least leaves the cargo cache in the user's home directory in place.
For some context: On #504, coverage failed with a somewhat strange behavior. While a locally generated report looked fine, the report on Coveralls looked rather strange.
Snippet from local report: Snippet from Coveralls report: