We ran into this issue a couple of months ago - I'm not sure how helpful this is but just in case extra information is useful I'll share our workarounds. The faulthandler output was roughly the same - the error happened during a rollback. This also happened on multiple python and sqlite versions.
It started when we removed a model and the one foreign key to that model. The quickest workaround we found was to simply add the model and foreign key back when running tests - which implies to me that the structure of the database was related to whether or not it segfaulted (the test where the segfault occurred was unrelated to the model that was removed). The second option was we could remove the creation of a model during a test (i.e. something that meant a rollback was required). The third option was to use an on-disk sqlite database rather than in memory. I hope some of that is useful, Sam On Thu, 7 Apr 2016 at 14:37 Florian Apolloner <f.apollo...@gmail.com> wrote: > This is the list of SQL statements we are executing: > https://dpaste.de/Mqu1/raw first column is thread id, second is cursor id > and third is the statement. I am a little bit confused about why the cursor > ids seem to be "jumpy" like that -- but in general this should not cause > issues I think > > > On Thursday, April 7, 2016 at 3:06:14 PM UTC+2, Florian Apolloner wrote: >> >> Perfect, I can reproduce it. This also happens if the default/other >> databases are not in memory -- I'll see what happens if I switch to >> postgres for the second database (though I am getting an error there >> currently -- might have to fix master :D) >> >> On Thursday, April 7, 2016 at 1:00:25 PM UTC+2, Raphael Hertzog wrote: >>> >>> [ CCing an upstream developer of SQlite too ] >>> >>> Hello, >>> >>> I did not want to open a ticket as I'm not sure if the problem >>> is in SQLite or in Django but the Django test suite fails really badly >>> with SQLite 3.12.0 that got recently released (and which is already >>> in Debian Unstable). >>> >>> When using the default --parallel run, I get many weird >>> errors and sometimes even a deadlock. When I run it with --parallel=1, >>> I got a segfault. >>> >>> You can see a log of the failure here (this is a parallel run): >>> >>> https://ci.debian.net/data/packages/unstable/amd64/p/python-django/20160406_191352.autopkgtest.log.gz >>> >>> There's a backtrace of the segfault (with --parallel=1): >>> >>> https://bugs.debian.org/cgi-bin/bugreport.cgi?filename=gdb.txt;bug=820225;msg=27;att=1 >>> >>> Cheers, >>> >>> PS: Tracked here in Debian too: >>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820225 >>> -- >>> Raphaël Hertzog ◈ Writer/Consultant ◈ Debian Developer >>> >>> Discover the Debian Administrator's Handbook: >>> → http://debian-handbook.info/get/ >>> >> -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/813967fd-3a1f-4b2a-93cc-c14f320f920f%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/813967fd-3a1f-4b2a-93cc-c14f320f920f%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyx3A1YcqPkzUNboc%3DntngpAyLjLJ_9gy5vfZ_b5pxyqGjZrQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
