#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 AlexRiina):
I ran into this after an update to django1.8.6. I was able to trace it
down to a test that wasn't crashing but was missing a `super(MyTest,
cls).tearDownClass()`. The test that actually crashed used
`override_settings` and adding either the super `tearDownClass` or
removing the `override_settings` resolved the issue for me.
Unfortunately, coming up with an example is proving hard because I'm only
seeing the segfault much later (I don't see the error when running the
test with a missing `tearDownClass` and then the test with
`override_settings` even though I see the error when I run the full
suite).
{{{
class MyTest(TestCase):
@classmethod
def tearDownClass(cls):
pass
...
@override_settings(...)
class MyOtherTest(TestCase):
pass
}}}
I'll try to distill this to a full example.
--
Ticket URL: <https://code.djangoproject.com/ticket/24080#comment:44>
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.4c44e97ce6ddb8963daf40042b8dc652%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
