#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 nose | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+------------------------------------
Comment (by stebunovd):
Colleague of mine discovered a workaround - try renaming test methods to
change their execution order. For example, rename the method on which
Segmentation fault occurs to be the first in its test class (in
alphabetical order). Sounds weird, but it worked both for him and for me.
--
Ticket URL: <https://code.djangoproject.com/ticket/24080#comment:54>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.7e76fab398f5e165dfac43f6f990648f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
