Opened 3 years ago
Last modified 3 years ago
#33356 closed Bug
"python manage.py test" fails, but running the individual TestCase pass — at Initial Version
| Reported by: | Dylan Yung | Owned by: | nobody |
|---|---|---|---|
| Component: | Uncategorized | Version: | 3.2 |
| Severity: | Normal | Keywords: | |
| Cc: | Egor R | Triage Stage: | Unreviewed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
There's some weird internal Django bug with views that use "transaction.atomic()" if you ping that view with multiple TestCase a weird bug will happen where there's a DB check at the end of tests after the DB has been torn down. I made 2 StackOverflow posts regarding this issue and found the fix as well. Hopefully there'll be an internal fix.
https://stackoverflow.com/questions/70105907/django-full-test-suite-failing-when-adding-a-testcase-but-full-test-suite-pas/70312267#70312267
https://stackoverflow.com/questions/70166752/django-serializer-throwing-invalid-pk-object-does-not-exist-when-setting-m
Note:
See TracTickets
for help on using tickets.