#35548: An error in TestCase.setUpTestData() leaks data on databases without
transactions
-----------------------------------+--------------------------------------
Reporter: Tim Graham | Owner: JaeHyuckSa
Type: Bug | Status: assigned
Component: Testing framework | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Comment (by blighj):
In their defence, there is guidance that says members can mark tickets
ready for checkin
https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
tickets/#ready-for-checkin
>The ticket was reviewed by any member of the community other than the
person who supplied the patch and found to meet all the requirements for a
commit-ready contribution. A merger now needs to give a final review prior
to being committed.
https://forum.djangoproject.com/t/django-ticket-status-change/16239
It does sort of elude that if a member things a patch meets all the
requirements they can mark it ready for checkin
I know it's not the usual practise though.
--
Ticket URL: <https://code.djangoproject.com/ticket/35548#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 visit
https://groups.google.com/d/msgid/django-updates/0107019d0ca6bb13-4ad060de-432c-4ed0-a46e-cf7620f30d70-000000%40eu-central-1.amazonses.com.
