Skip to content

Unblock DB in case of error for reports#778

Closed
blueyed wants to merge 3 commits intopytest-dev:masterfrom
blueyed:unblock-db-for-report
Closed

Unblock DB in case of error for reports#778
blueyed wants to merge 3 commits intopytest-dev:masterfrom
blueyed:unblock-db-for-report

Conversation

@blueyed
Copy link
Contributor

@blueyed blueyed commented Oct 23, 2019

This mainly works around pytest causing an INTERNALERROR for when using
repr() on the pytest.fail.Exception that is used when the DB is
blocked.

While this will be fixed via
pytest-dev/pytest#6047 likely, it might be good
to have this anyway (also for older pytest versions).

On the other hand this might cause the DB to be accessed/changed then,
which might show different results from when the test failed due to
this?!

Fixes #713.
Fixes #341.

This mainly works around pytest causing an INTERNALERROR for when using
`repr()` on the `pytest.fail.Exception` that is used when the DB is
blocked.

While this will be fixed via
pytest-dev/pytest#6047 likely, it might be good
to have this anyway (also for older pytest versions).

On the other hand this might cause the DB to be accessed/changed then,
which might show different results from when the test failed due to
this?!

Fixes pytest-dev#713.
Fixes pytest-dev#341.
@blueyed
Copy link
Contributor Author

blueyed commented Nov 1, 2019

Going with #781 instead.

@blueyed blueyed closed this Nov 1, 2019
@blueyed blueyed deleted the unblock-db-for-report branch November 1, 2019 13:53
blueyed added a commit to blueyed/pytest-django that referenced this pull request Nov 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

INTERNALERROR> Failed: Database access not allowed _django_db_setup fails with data migrations

1 participant