#32409: TestCase async tests are not transaction-aware
-------------------------------------+-------------------------------------
Reporter: David | Owner: nobody
Type: New feature | Status: new
Component: Testing framework | Version: 3.1
Severity: Normal | Resolution:
Keywords: TestCase, async, | Triage Stage: Accepted
transaction |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Andrew Godwin):
No, that's plenty new, the change happened in 3.3.0. In that case, I think
the best course of investigation here is why the outer sync thread with
the transaction in it, and the inner sync thread the ORM runs in, are
different. I can take a look at that in a few weeks, but unfortunately I'm
pretty busy at work right now so I can't do it immediately.
If anyone else is interested in doing that investigation, the thing I
normally do is go edit the Django source code at relevant points and make
it print the current thread ID, then run a test and see what thread IDs
get printed out during it.
--
Ticket URL: <https://code.djangoproject.com/ticket/32409#comment:11>
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.49e4ee66b773a20f9d08251c8c29f877%40djangoproject.com.
