You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We seem to have an issue in our test setup with pytest-django and the new 8.0.0 release of pytest. Just pinning pytest to the last 7.x version is a working workaround for us.
Our database setup fixture is crashing since the new pytest version was released. I am not sure which component is ultimately responsible for this bug, but I figured I could try pinging you first as it might be very well in pytest-django.
This is the error we are getting. It looks like it is trying to setup the db to often and thus generates too long database names as a side effect.
Begin of the stack trace
pytest_django/fixtures.py:305: in handle shows up 293 times in total. Looks like some kind of recursive loop
We also see this sometimes after upgrading to pytest 8.0.0.
Debugged a bit and noticed after running tests for some time at a certain time in pytest-django in method django_db_modify_db_settings_xdist_suffix the value of the test database name seems wrong.
I see these values:
suffix = 'gw2'
test_name = 'test_gw2'
This means after the method returns the database name will be test_gw2_gw2.
We seem to have an issue in our test setup with
pytest-django
and the new 8.0.0 release of pytest. Just pinning pytest to the last 7.x version is a working workaround for us.Our database setup fixture is crashing since the new pytest version was released. I am not sure which component is ultimately responsible for this bug, but I figured I could try pinging you first as it might be very well in
pytest-django
.This is the error we are getting. It looks like it is trying to setup the db to often and thus generates too long database names as a side effect.
Begin of the stack trace
pytest_django/fixtures.py:305: in handle
shows up 293 times in total. Looks like some kind of recursive looppytest 8.0.0
Django 4.2.9
pytest-django 4.7.0
Python 3.10.13
Debian
Postgres
The text was updated successfully, but these errors were encountered: