#18984: TransactionTestCase._fixture_teardown locks under mysql
---------------------------------------------+------------------------
Reporter: jdunck | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: master
Severity: Release blocker | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
---------------------------------------------+------------------------
When using multiple aliases to the same DB (either via TEST_MIRROR or
simply different aliases with the same settings), it is possible to get 2
pending transactions because each DB alias gets its own connection to the
DB.
The change in [https://github.com/django/django/commit/f758bdab f758bdab]
moves DB flush to the end of the test case -- this is nice because it
allows test case reordering and related optimizations.
Unfortunately, moving it to the end also means that the DB connection
states aren't as clean as they were at the beginning of the testcase, so
it's possible that a pending transaction on one alias blocks the progress
of the flush command.
--
Ticket URL: <https://code.djangoproject.com/ticket/18984>
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 https://groups.google.com/groups/opt_out.
