Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Incorrect coverage report
See original GitHub issueUsing py.test --cov-config .coveragerc --cov nengo -n 6 nengo a lot of lines that should be hit get reported as missed (like class and function definitions in a module). This might be related to #19 as the project has a conftest file importing other modules from the project.
Using coverage run --rcfile .coveragerc --source nengo -m py.test nengo instead a correct coverage report is generated, but this command does not support xdist.
Issue Analytics
- State:
- Created 7 years ago
- Comments:21 (11 by maintainers)
Top Results From Across the Web
Wrong coverage report · Issue #375 · vitest-dev/vitest - GitHub
Describe the bug The coverage doesn't make sense with the actual code Reproduction Github repo: ... Wrong coverage report #375.
Read more >Code coverage report seems incorrect. Why? - Google Groups
Hello. I use Jacoco with ant and then use sonar to reuse jacoco.exec to show the result. But the result seems incorrect. What's...
Read more >Incorrect coverage number reported by codecov - Bug Fixes
The local jacoco report (screenshot below) shows about 85% coverage. The problem is codecov reporting only 20% while jacoco reports 85%. image.
Read more >Incorrect coverage report: unchanged lines of code in Java CI ...
We've integrated Sonar using GitHub Actions, but it reports 371 lines of code changing in the PR when 0 are modified.
Read more >Coverage Report displaying incorrect results when ... - YouTrack
As a further proof, when I run the same unit tests outside of pycharm with the pypi coverage module generated it will shows...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Afaik it’s either the workaround I use in pytest-benchmark (forceload pytest-cov subprocess engine) or ronny’s plugin trick (haven’t tried it).
This is fixed right? Also, #177 will clarify the solutions.