#24080: Sqlite segmentation fault regression when running tests (since 1.7.2)
-----------------------------------+------------------------------------
     Reporter:  stevejalim         |                    Owner:  nobody
         Type:  Bug                |                   Status:  new
    Component:  Testing framework  |                  Version:  master
     Severity:  Normal             |               Resolution:
     Keywords:  sqlite             |             Triage Stage:  Accepted
    Has patch:  0                  |      Needs documentation:  0
  Needs tests:  0                  |  Patch needs improvement:  0
Easy pickings:  0                  |                    UI/UX:  0
-----------------------------------+------------------------------------

Comment (by timgraham):

 #25860 seems to be a duplicate and also points to a case where
 `django.test.TestCase` fails to be called (if `skipTest` is raised in
 `setUpClass()`. The original report is about a regression in 1.7.2 but the
 subsequent reports seem to be for 1.8 and related to `setUpTestData()` so
 it seems we should retitle this issue, create a new one, or use #25860
 (closing this one as needsinfo since we still don't have anything to
 reproduce a problem on 1.7.2). It's not immediately to me if/how we'd fix
 the problem since it's somewhat related to user code, but maybe we can at
 least do better to detect the situation or document it.

--
Ticket URL: <https://code.djangoproject.com/ticket/24080#comment:45>
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 post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.b09e57e0bc5d2907d2ab52dfa56754e7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to