Changes between Initial Version and Version 1 of Ticket #37077


Ignore:
Timestamp:
Apr 29, 2026, 3:57:29 PM (3 weeks ago)
Author:
Jacob Walls
Comment:

Oh, this is going to be fun. I'm surprised that AttributeError doesn't cause a non-zero exit. If I throw an AttributeError inside initialize_suite, I get a nice failure. What's going on there?

Can you share the DATABASES you reproduced with, so we can see how your ["TEST"]["MIRROR"] is configured?

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #37077

    • Property Component Database layer (models, ORM) → Testing framework
    • Property Type Uncategorized → Bug

  • Ticket #37077 – Description

    initial v1  
    11In a very specific situation, the test runner skips running tests, and just terminates (successfully). Instead of running the tests, the database is set up, cloned for each process, then destroyed without running any tests. This is related to the changes from #35967
    22
    3 With a `TransactionTestCase` with `serialized_rollback=True`, and a project with multiple `DATABASES` where one is a mirror of the other, where both connections are needed for the test (eg `databases = "__all__"). If a `TransactionTestCase` isn't going to be run, this behaviour isn't seen.
     3With a `TransactionTestCase` with `serialized_rollback=True`, and a project with multiple `DATABASES` where one is a mirror of the other, where both connections are needed for the test (eg `databases = "__all__"`). If a `TransactionTestCase` isn't going to be run, this behaviour isn't seen.
    44
    55The cause is that in `ParallelTestSuite.initialize_suite`, an `AttributeError` is raised when accessing `connections[alias]._test_serialized_contents`, because contents is never set.
Back to Top