-
Notifications
You must be signed in to change notification settings - Fork 211
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
Noisy CoverageWarnings No source for code in pep517-build-env #538
Comments
I notice that the warnings go away if I run with |
This issue no longer seems to be a problem. The repro no longer reproduces the issue, either because the pytest-checkdocs has evolved further or something has been fixed. Regardless, I'm going to go ahead and close this issue and back out the workaround. |
This reverts commit e719f86. The issue seems to have been addressed somehow. Ref pytest-dev/pytest-cov#538.
This reverts commit 1d8cec6. The issue seems to have been addressed somehow. Ref pytest-dev/pytest-cov#538.
Summary
Sometime in the past year, pytest-cov started emitting lots of CoverageWarnings for files unrelated to the project under test, something like:
I work with hundreds of projects that derive from jaraco/skeleton, where I reported the issue in jaraco/skeleton#56. An example project affected by this noise is jaraco/tempora.
Expected vs actual result
Simply run tox on that small project, and there's a 166 of those warnings. Since these files are unrelated to the project and since these warnings aren't emitted when running coverage natively, I'd expect these warnings not to emit when running using pytest-cov.
In addition to the warnings about
pep517-build-env
, there's one additional about a file calledsetup.py
in the root of the project, which also doesn't exist. It would be nice to fix both, but this report focuses mainly on those created by files in thepep517-build-env
.Reproducer
Note that the errors happen whether tox is invoked or not. Just using tox to set up the environment and then running
pytest
produces the same warnings. See jaraco/skeleton#56 for more details on the output in both cases.Versions
Here's the current output of tox and pytest:
Config
See the jaraco/skeleton repo for the generic config used across projects or look at jaraco/tempora for a materialized project.
I plan to merge jaraco/skeleton#60 to work around the issue, but it would be nice if the issue could be addressed at the cause and not at the symptom.
The text was updated successfully, but these errors were encountered: