Opened 7 months ago

Closed 7 months ago

#33356 closed Bug (needsinfo)

"python test" fails, but running the individual TestCase pass

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 (last modified by Dylan Yung)

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.

Because Django tests the db transaction processing mechanism, the real test part is finish and success, and then it will rollback the data(data flush),so some db level check is no use and misleading.

so we need modify the foreign key check defer to make it get right result.

I'm using a postgres DB

Change History (4)

comment:1 Changed 7 months ago by Dylan Yung

Description: modified (diff)

comment:2 Changed 7 months ago by Dylan Yung

Description: modified (diff)

comment:3 Changed 7 months ago by Egor R

Cc: Egor R added

comment:4 Changed 7 months ago by Tim Graham

Resolution: needsinfo
Status: newclosed

It's not clear to me that Django is at fault. The accepted answer on Stackoverflow says, "There's some weird internal bug where if you operate on one table a lot with a lot of different TestCase classes then it'll do a DB check at the end after it's been torn down and it'll cause an error." but it's not clear that this is just speculation.

You need to at least provide a far simpler minimal example to reproduce the problem, and ideally, explain why Django is at fault. Thanks.

Note: See TracTickets for help on using tickets.
Back to Top