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/d74755bd-b281-4d29-88c1-884719ed26a2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
