-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Failing pytester tests with features branch #2946
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
Comments
Bisected to pytest-dev/pluggy@4776698 - cc @tgoodlet I guess some hook in pytest-cov isn't called anymore or something? Haven't tried reproducing it outside of that test yet. |
I tried reproducing it with a minimal test: pytest_plugins = 'pytester'
def test_foo(testdir):
testdir.makepyfile(mod="""
def func():
pass
""")
testdir.makepyfile(test_mod="""
import mod
def test_func():
mod.func()
""")
testdir.runpytest('--cov=mod', '--cov-report=xml')
assert (testdir.tmpdir / 'coverage.xml').exists() but that passes. I'm out of ideas for now 😟 |
Ah, I think I understand now! This happens because I use |
Thanks for debugging this @The-Compiler! I see two options:
What should we do next? |
Well, failing all testsuites which use Seeing that there's already a fix at pytest-dev/pluggy#94 I propose merging that and doing a new pluggy release first. |
I agree. @RonnyPfannschmidt and @tgoodlet what do you guys think? |
@nicoddemus @The-Compiler sorry, late getting back to you guys. Yes I think this is a good idea although I think only a patch release should be necessary no? |
The next pluggy version is |
|
Awesome @tgoodlet, thanks! @The-Compiler would you mind give this another go and make sure this fixes the issue? |
Sorry, I forgot about this - seems fine nowadays! |
@nicoddemus Let's continue the discussion from #2945 here, as this probably warrants some deeper investigation.
When trying to run my tests (after some patching), I get various failures in my test_check_coverage.py which runs pytest via
pytester
and produces acoverage.xml
viapytest-cov
which it then reads.Here's how it fails:
I was able to bisect it to 333a9ad but that probably also did some kind of pluggy update?
The text was updated successfully, but these errors were encountered: