Opened 15 years ago
Closed 15 years ago
#8059 closed (fixed)
m2m_through test hasn't a really predictable output
| Reported by: | Ramiro Morales | Owned by: | nobody |
|---|---|---|---|
| Component: | Testing framework | Version: | dev |
| Severity: | Keywords: | m2m_through db backend output modeltests | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
One of the tests for this new functionality:
http://code.djangoproject.com/browser/django/trunk/tests/modeltests/m2m_through/models.py#L329
runs successfully with all (some?) the builtin DB backends, but from what can be seen in the model definitions and the data handling made in the tests leading to that specific test, there isn't an unique 'correct' output order.
This is showing a a failure when running the test suite against another external DB backend.
The attached patch solves this adding another item to the membership.meta.ordering tuple.
Attachments (1)
Change History (4)
Changed 15 years ago by
| Attachment: | t8059.diff added |
|---|
comment:1 Changed 15 years ago by
| Has patch: | set |
|---|
comment:2 Changed 15 years ago by
comment:3 Changed 15 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Looks like this is also failing with the mysql backend: http://certenium.ingenium.cl:8080/hudson/job/django-trunk/SETTINGS_MODULE=settings_mysql/26/testReport/modeltests.m2m_through.models/__test__/API_TESTS/