#32403: When run test with off postgres database got `RuntimeError: generator
didn't yield` instead of connection error
-------------------------------------+-------------------------------------
Reporter: Kazantcev Andrey | Owner: Mariusz
| Felisiak
Type: Bug | Status: closed
Component: Database layer | Version: 3.1
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: postgres db | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"7d658893450eb999f828c53a8e4efa03dff65cf3" 7d658893]:
{{{
#!CommitTicketReference repository=""
revision="7d658893450eb999f828c53a8e4efa03dff65cf3"
[3.2.x] Fixed #32403 -- Fixed re-raising DatabaseErrors when using only
'postgres' database.
Thanks Kazantcev Andrey for the report.
Regression in f48f671223a20b161ca819cf7d6298e43b8ba5fe.
Backport of f131841c601b9d4884adcdb284b4213c2ad89231 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32403#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.f18e1b295117998129dfd2d040037b55%40djangoproject.com.