#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 rhertzog):

 Since the switch to SQLite 3.12 I can reproduce a similar segfault (same
 stacktrace output by faulthandler) with Django 1.9.5 and Python 2.7.11 or
 3.5.1.

 {{{
 $ cd tests
 $ PYTHONPATH=.. python3 -X faulthandler ./runtests.py --verbosity=2
 --parallel=1 admin_views.tests.AdminViewBasicTest
 [...]
 test_popup_dismiss_related (admin_views.tests.AdminViewBasicTest) ... ok
 Fatal Python error: Segmentation fault

 Current thread 0x00007fab40575700 (most recent call first):
   File "/home/rhertzog/deb/pkg/python-
 django/django/db/backends/sqlite3/base.py", line 321 in execute
   File "/home/rhertzog/deb/pkg/python-django/django/db/backends/utils.py",
 line 62 in execute
   File "/home/rhertzog/deb/pkg/python-
 django/django/db/backends/base/base.py", line 288 in _savepoint_rollback
   File "/home/rhertzog/deb/pkg/python-
 django/django/db/backends/base/base.py", line 328 in savepoint_rollback
   File "/home/rhertzog/deb/pkg/python-django/django/db/transaction.py",
 line 243 in __exit__
   File "/home/rhertzog/deb/pkg/python-django/django/test/testcases.py",
 line 1016 in _rollback_atomics
   File "/home/rhertzog/deb/pkg/python-django/django/test/testcases.py",
 line 1073 in _fixture_teardown
   File "/home/rhertzog/deb/pkg/python-django/django/test/testcases.py",
 line 919 in _post_teardown
   File "/home/rhertzog/deb/pkg/python-django/django/test/testcases.py",
 line 217 in __call__
   File "/usr/lib/python3.5/unittest/suite.py", line 122 in run
   File "/usr/lib/python3.5/unittest/suite.py", line 84 in __call__
   File "/usr/lib/python3.5/unittest/runner.py", line 176 in run
   File "/home/rhertzog/deb/pkg/python-django/django/test/runner.py", line
 494 in run_suite
   File "/home/rhertzog/deb/pkg/python-django/django/test/runner.py", line
 533 in run_tests
   File "./runtests.py", line 275 in django_tests
   File "./runtests.py", line 458 in <module>
 }}}

 Maybe SQLite 3.12 makes it more likely to trigger to the problem or
 something like that...

--
Ticket URL: <https://code.djangoproject.com/ticket/24080#comment:51>
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.c7ab190f48592676b3adf000c30892af%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to