#33161: Do not ignore transaction durability errors within TestCase
-------------------------------------+-------------------------------------
Reporter: Krzysztof Jagiełło | Owner: Krzysztof
| Jagiełło
Type: New feature | 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 Krzysztof Jagiełło):
Replying to [comment:14 David Seddon]:
> It reminds me of the difficulties of testing code that uses
`select_for_update`. I have seen many occasions where wrapped test cases
are the only coverage of such code, and we don't see the issue until it
hits production.
Got hit by that one to in the past too! I think that once this patch gets
merged we should be able to apply a similar fix to `select_for_update`
too.
Regarding the patch, I have decided to keep working on my PR
(https://github.com/django/django/pull/14919) as the one proposed by Adam
did not work for sequential durable transactions (see the repro case in my
previous comment). Let me know if there is anything you would like me to
adjust in my PR before its merge-ready.
--
Ticket URL: <https://code.djangoproject.com/ticket/33161#comment:15>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.cc89606adaf153a3902a0faff3a9edb5%40djangoproject.com.
