Closed agateblue closed 4 years ago
Hi @EliotBerriot,
Thanks for the report! Seems to be the same issue as in #6492. The workaround for now is to pin pytest to 5.3.2 until we figure out if the problem is in pytest or pytest-django. 👍
Closing this one in favor of #6492, please subscribe to it to get notifications on the progress of this problem. 👍
@EliotBerriot
It might be useful to run it with -l
to show locals in the traceback (to see what those finish calls are about), and/or put a pdb.set_trace()
/print
there to see if it is the same fixture all the time.
/cc @SalmonMode I think this might be interesting for debugging.
My test suite fails consistently at 99% (e.g https://dev.funkwhale.audio/funkwhale/funkwhale/-/jobs/40524) when using Pytest 5.3.3. The issue doesn't seem to occur when using Pytest 5.3.2, so I suspect it is a regression.
Fortunately, I seem to reproduce the issue when running only a fraction of my test suite, e.g:
At first, since the error seemingly occured at the very end of the test suite, I suspected a broken interaction with a plugin, so I uninstalled a few of them (xdist, forked, profiling, cov, sugar), but it's still failing:
I've also tried to isolate a specific test that could cause this issue, by runnining only a subset of the tests, but I couldn't isolate one this way. However, I did find an interesting outcome! With the 110 tests uncommented, I get the
core dumped
issues. But when I commented tests one by one, at one point, I got a recursion error:I don't have the time to provide a minimal example right now, but I can definitely give more information or try some commands, since I reliably reproduce this in my dev environment, inside a Docker container running Linux Alpine and Python 3.6.8.
pip freeze
output:By the way, many thanks to the Pytest community for the amazing piece of software :heart: Let me know if I can provide anything else to troubleshoot this.