For the record, the discussion continues here:
https://www.sqlite.org/src/info/7f7f8026eda38
--
Aymeric.
> On 07 Apr 2016, at 18:27, Florian Apolloner wrote:
>
> mkdir ~/sqlite
> cd ~/sqlite
> git clone g...@github.com:django/django.git
> git clone g...@github.com:apollo13/sqlite_bug.git
> exp
mkdir ~/sqlite
cd ~/sqlite
git clone g...@github.com:django/django.git
git clone g...@github.com:apollo13/sqlite_bug.git
export PYTHONPATH=`pwd`/django
cd sqlite_bug
gdb python
(in gdb shell) r ./manage.py test admin_views
Please tell me if this does not cause a segfault for you.
Cheers,
Florian
I've created an application which shows the behavior:
https://github.com/apollo13/sqlite_bug -- I cannot yet reproduce it without
running it through the testing process -- ./manage.py test admin_views
triggers the bug in this application!
On Thursday, April 7, 2016 at 3:37:14 PM UTC+2, Florian
I was able to reduce the admin_view testcases to
https://github.com/apollo13/django/blob/f086934f02efaca272e7e9b29921a31fd47821aa/tests/admin_views/tests.py
(see my sqlite_segfault branch)
On Thursday, April 7, 2016 at 3:06:14 PM UTC+2, Florian Apolloner wrote:
>
> Perfect, I can reproduce it.
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.
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
Le jeudi 07 avril 2016, Aymeric Augustin a écrit :
> This other ticket about a SQLite segfault may or may not be related:
> https://code.djangoproject.com/ticket/24080
Given how old it is, I was tempted to say it's entirely unrelated. But
maybe not. I discovered faulthandler thanks to this and the
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,
This other ticket about a SQLite segfault may or may not be related:
https://code.djangoproject.com/ticket/24080
--
Aymeric.
> On 07 Apr 2016, at 13:00, 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
[ 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 defau
10 matches
Mail list logo
