[Django] #20725: Oracle+Python3: Django test suite segfaults

6 views
Skip to first unread message

Django

unread,
Jul 9, 2013, 6:10:35 PM7/9/13
to django-...@googlegroups.com
#20725: Oracle+Python3: Django test suite segfaults
-------------------------------+----------------------------
Reporter: shai | Owner: shai
Type: Bug | Status: new
Component: Uncategorized | Version: 1.6-beta-1
Severity: Normal | Keywords: oracle python3
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+----------------------------
A segfault is generated when running the full test
`select_related_onetoone.tests.ReverseSelectRelatedTestCase`. The segfault
happens on different tests within this class, depending on details of the
invocation (and version of Python3), but the test-case always creates a
segfault.

Tested on Debian Testing (amd64), against cx_Oracle 5.1.2 (latest released
at this point), Oracle instant client 11.2.0.3.0, and Oracle server 11g
release 11.2 Enterprise Edition;

Tested on both master and the 1.6 branch;

Tested with:

System's python3:
{{{
Python 3.2.4 (default, May 8 2013, 20:55:18)
[GCC 4.7.3] on linux2
}}}
Self-built Python 3.3.1:
{{{
Python 3.3.1 (default, May 6 2013, 16:18:33)
[GCC 4.7.2] on linux
}}}
Self-built Python 3.3.2:
{{{
Python 3.3.2 (default, Jul 10 2013, 00:09:35)
[GCC 4.7.3] on linux
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/20725>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Jul 25, 2013, 9:53:21 AM7/25/13
to django-...@googlegroups.com
#20725: Oracle+Python3: Django test suite segfaults
-----------------------------------+--------------------------------------

Reporter: shai | Owner: shai
Type: Bug | Status: new
Component: Testing framework | Version: 1.6-beta-1
Severity: Normal | Resolution:
Keywords: oracle python3 | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Changes (by timo):

* needs_docs: => 0
* needs_better_patch: => 0
* component: Uncategorized => Testing framework
* needs_tests: => 0
* stage: Unreviewed => Accepted


--
Ticket URL: <https://code.djangoproject.com/ticket/20725#comment:1>

Django

unread,
Jul 25, 2013, 3:46:44 PM7/25/13
to django-...@googlegroups.com
#20725: Oracle+Python3: Django test suite segfaults
-------------------------------------+-------------------------------------

Reporter: shai | Owner: shai
Type: Bug | Status: new
Component: Database layer | Version:
(models, ORM) | 1.6-beta-1

Severity: Normal | Resolution:
Keywords: oracle python3 | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by shai):

* component: Testing framework => Database layer (models, ORM)


Comment:

It's a problem with the Oracle backend (or, rather, its dependencies), not
with the testing framework.

--
Ticket URL: <https://code.djangoproject.com/ticket/20725#comment:2>

Django

unread,
Jun 13, 2014, 8:40:22 PM6/13/14
to django-...@googlegroups.com
#20725: Oracle+Python3: Django test suite segfaults
-------------------------------------+-------------------------------------
Reporter: shai | Owner: shai
Type: Bug | Status: closed

Component: Database layer | Version:
(models, ORM) | 1.6-beta-1
Severity: Normal | Resolution: fixed

Keywords: oracle python3 | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timo):

* status: new => closed
* resolution: => fixed


Comment:

This is fixed with cx_Oracle 5.1.3 per [https://groups.google.com/d/topic
/django-developers/6FLjKkVRx2Y/discussion Shai]. I have also been able to
run the tests on Oracle with Python 3.

--
Ticket URL: <https://code.djangoproject.com/ticket/20725#comment:3>

Reply all
Reply to author
Forward
0 new messages