#31752 closed Bug (fixed)
Intermittent test failure on Windows with PostgreSQL
Reported by: | Carlton Gibson | Owned by: | Carlton Gibson |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | dev |
Severity: | Normal | Keywords: | Tests, Windows |
Cc: | Ahmad A. Hussein | Triage Stage: | Accepted |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Reported by Ahmad on the forum, there's an intermittent test failure with Windows+Postgres.
(django) PS C:\Users\carlt\src\django\tests> python .\runtests.py --settings=test_postgres m2m_through.tests.M2mThroughTests Testing against Django installed in 'c:\users\carlt\src\django\django' Creating test database for alias 'default'... System check identified no issues (0 silenced). .....................F................... ====================================================================== FAIL: test_order_by_relational_field_through_model (m2m_through.tests.M2mThroughTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "C:\Users\carlt\src\django\tests\m2m_through\tests.py", line 247, in test_order_by_relational_field_through_model [self.jim, self.bob] AssertionError: Sequences differ: <QuerySet [<Person: Person object (1)>, <Person: Person object (2)>]> != [<Person: Person object (2)>, <Person: Person object (1)>] First differing element 0: <Person: Person object (1)> <Person: Person object (2)> - <QuerySet [<Person: Person object (1)>, <Person: Person object (2)>]> ? ---------- ^ ^ - + [<Person: Person object (2)>, <Person: Person object (1)>] ? ^ ^ ---------------------------------------------------------------------- Ran 41 tests in 0.264s FAILED (failures=1) Destroying test database for alias 'default'...
Looks like a non-deterministic ordering problem.
Reproduced at 615e32162ff646db3456b90fb4eaaecc33dd3e4e.
Change History (3)
comment:1 by , 4 years ago
Has patch: | set |
---|---|
Owner: | changed from | to
Status: | new → assigned |
Note:
See TracTickets
for help on using tickets.
PR -- see if that works...