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
Describe the bug
we have two databases in our django application. it works well to run command "python manage.py runserver 0.0.0.0:8000"
but it stuck when run coverage "coverage run manage.py test --with-xunit" with the message below.
coverage run manage.py test --with-xunit
nosetests --with-xunit --verbosity=1
Using existing test database for alias 'default'...
Using existing test database for alias 'price'...
in fact, the test_default db is done and for the test_price db, the db is created but no one table is created. it seems that the setup process is halted by something when creating table for test_price db.
django's backend
Switch to django's backend (django.db.backends.postgresql), everything is ok.
Environment
Python Version: 3.8.19
Django Version: 2.2.28
The text was updated successfully, but these errors were encountered:
Describe the bug
we have two databases in our django application. it works well to run command "python manage.py runserver 0.0.0.0:8000"
but it stuck when run coverage "coverage run manage.py test --with-xunit" with the message below.
coverage run manage.py test --with-xunit
nosetests --with-xunit --verbosity=1
Using existing test database for alias 'default'...
Using existing test database for alias 'price'...
in fact, the test_default db is done and for the test_price db, the db is created but no one table is created. it seems that the setup process is halted by something when creating table for test_price db.
django's backend
Switch to django's backend (
django.db.backends.postgresql
), everything is ok.Environment
The text was updated successfully, but these errors were encountered: