#14250 closed (fixed)
FileBasedCacheTests.test_cull test failure
| Reported by: | Luke Plant | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Cache system) | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Since r13678, I'm getting this test failure:
======================================================================
FAIL: test_cull (regressiontests.cache.tests.FileBasedCacheTests)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/luke/devel/django/trunk/tests/regressiontests/cache/tests.py", line 430, in test_cull
self.perform_cull_test(50, 28)
File "/home/luke/devel/django/trunk/tests/regressiontests/cache/tests.py", line 367, in perform_cull_test
self.assertEqual(count, final_count)
AssertionError: 27 != 28
This happens whether I run just the single test or many others. This does not appear to be causing test failures for anyone else (like Russell who checked it in, or the buildbots), but it is happening on a clean checkout on my Ubuntu Lucid box, Python 2.4/2.5/2.6, and on a CentOS 5.5 box, Python 2.4.
I don't have access to a box where the test passes to see what is different, and I cannot track down any source of non-deterministic behaviour, so this has me stumped for now.
Change History (2)
comment:1 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 14 years ago
Note:
See TracTickets
for help on using tickets.
(In [13705]) Fixed #14250 - FileBasedCacheTests.test_cull test failure
This patch makes the cull behaviour (which files deleted and how many
deleted) deterministic.