New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[run] omit is ignored since 4.5 #638
Comments
@mgedmin Can you point me to the commit in your repo that shows the problem? And exactly how to reproduce the before/after? |
Original comment by Marius Gedminas (Bitbucket: mgedmin, GitHub: mgedmin) mgedmin/irclog2html@da8d6ec is a commit where (The "Also for some reason buildout-installed tools ignore my .coveragerc" part of the commit message was a misunderstanding on my part: buildout installed coverage 4.5 and was affected by this bug, but my globally pip-installed coverage was still at 4.4.) mgedmin/irclog2html@3db55bd is the workaround I applied to get the reporting back to 100%. |
Thanks. Looking at the .coverage files produced by 4.4.2 and 4.5, they are identical. So the |
The problem was that during measurement, omitting patterns weren't used inside source packages, only source directories. In the ambiguous case (such as you have) we interpret the source setting as a package. So the omit was being ignored (and has been for a while). It used to be that run-omit was also used for report-omit, so the data would be collected, but then omitted during reporting. Now that report-omit doesn't default to report-omit, the incorrectly collected data was being reported. In change 3ee6ac71eb08 (bb) I fixed the handling of omits inside source packages, so this is now fixed. |
This is now available in 4.5.1. |
Originally reported by Marius Gedminas (Bitbucket: mgedmin, GitHub: mgedmin)
The coverage of irclog2html dropped from 100% to 98% after a cron-triggered Travis CI rebuild with no code changes. I investigated and discovered that despite my .coveragerc containing
the new version of coverage (4.5) does not omit src/irclog2html/tests/test_*.py from measurement or reporting.
This is probably related to commit 1031ead7ca4c (bb).
The text was updated successfully, but these errors were encountered: