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
pytet 5.3.3 was just released today, and pytest-django performs very slowly and incorrectly when run with pytest-xdist. There is a tracking issue up at pytest-dev/pytest#6492, which includes a git-bisect run and a more detailed description.
The tl;dr is that due to a change in fixture handling, pytest-django plus pytest-xdist build increasingly long database names until you reach errors such as django.core.exceptions.ImproperlyConfigured: The database name 'test_travis_ci_test_gw0_gw0_gw0_gw0_gw0_gw0_gw0_gw0_gw0_gw0_gw0_gw0_gw0' (71 characters) is longer than PostgreSQL's limit of 63 characters. Supply a shorter NAME in settings.DATABASES., while performing very slowly.
The text was updated successfully, but these errors were encountered:
The other issue has by now determined that this is a problem that occurs around differently scoped fixtures and their teardown, so it's not pytest-django specific. Apologies for the duplicate issue.
pytet 5.3.3 was just released today, and pytest-django performs very slowly and incorrectly when run with pytest-xdist. There is a tracking issue up at pytest-dev/pytest#6492, which includes a git-bisect run and a more detailed description.
The tl;dr is that due to a change in fixture handling, pytest-django plus pytest-xdist build increasingly long database names until you reach errors such as
django.core.exceptions.ImproperlyConfigured: The database name 'test_travis_ci_test_gw0_gw0_gw0_gw0_gw0_gw0_gw0_gw0_gw0_gw0_gw0_gw0_gw0' (71 characters) is longer than PostgreSQL's limit of 63 characters. Supply a shorter NAME in settings.DATABASES.
, while performing very slowly.The text was updated successfully, but these errors were encountered: