#35368: Postgres schema test failure locally
-------------------------------------+-------------------------------------
Reporter: bcail | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: dev
(models, ORM) | Resolution:
Severity: Normal | worksforme
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by bcail):
I don't know the details of what's going wrong - I've been able to run
django's test suite fine, on sqlite & postgres, and then it started
failing, and I found that it was that commit where the problem started. I
was using psycopg2, and I just tried psycopg3, and it still failed.
Here is another detail, though: the test name that django gives as failing
is "test_add_generated_field" - but in the stacktrace, it points to the
test added in that commit ("test_add_generated_field_contains") - it seems
that django's printing the wrong test name in the error summary. If I set
`parallel=1` for the tests, then the correct test name gets shown in the
summary.
--
Ticket URL: <https://code.djangoproject.com/ticket/35368#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018ece8fa0c5-af8ed43b-38b5-4c2a-9a1d-a31900f4e1c5-000000%40eu-central-1.amazonses.com.
