#10868: _destroy_test_db exposes the production database to possibly destructive
actions from the unit tests
-------------------------------------+-------------------------------------
Reporter: ovidiu | Owner: nobody
Type: Bug | Status: closed
Component: Testing framework | Version:
Severity: Release blocker | Resolution: fixed
Keywords: django.test | Triage Stage: Ready for
Has patch: 1 | checkin
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by julien):
* status: new => closed
* resolution: => fixed
Comment:
In [17411]:
{{{
#!CommitTicketReference repository="" revision="17411"
Fixed #10868 -- Stopped restoring database connections after the tests'
execution in order to prevent the production database from being exposed
to potential threads that would still be running. Also did a bit of
PEP8-cleaning while I was in the area. Many thanks to ovidiu for the
report and to Anssi Kääriäinen for thoroughly investigating this issue.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/10868#comment:24>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
