-
Notifications
You must be signed in to change notification settings - Fork 347
Tests fail since pytest-django 3.4 for django-extensions #637
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
Thanks for the info! I would suggest first git-bisecting pytest-django, and if it is caused by some specific commit in there that might give a good clue. |
#638 fixes it. The problem is that "." gets inserted to |
That's interesting. I don't really get why inserting |
The problem in the tests is this:
And then there are a bunch of setup ERRORs, because of a missing |
It seems weird that |
Releasing 3.4.2 - will take a while due to builds on master being queued first: https://travis-ci.org/pytest-dev/pytest-django/builds/418313779 |
It seems like the module is imported before already, and then keeps the relative import os
import sys
sys.path.insert(0, '.')
# Importing it before chdir already causes failure.
import imported
os.chdir('/')
import imported
assert imported.__file__ == os.path.abspath(imported.__file__) |
Filed https://bugs.python.org/issue34444 for Python. |
Thanks for looking into this! 👍 |
I noticed that the tests of django-extensions@master fail since pytest-django 3.4 was released. See eg. https://travis-ci.org/michael-k/django-extensions/builds/417328508
When pinned to
pytest-django<3.4
intox.ini
the tests pass: https://travis-ci.org/michael-k/django-extensions/builds/417337453So far I could not figure out why. It says that
No fixture named 'group' found.
, but the changelog does not include anything helpful: https://github.com/pytest-dev/pytest-django/releases/tag/3.4.0 I also found no such fixture it the pytest-django 3.3.x codebase.If anyone has a clue where this might be coming from, please let me know or open a PR against the appropriate project.
The text was updated successfully, but these errors were encountered: