Opened 3 years ago

Closed 3 years ago

#19914 closed Bug (invalid)

MemcachedCacheTests failing on pylibmc

Reported by: bpeschier Owned by: nobody
Component: Core (Cache system) Version: master
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


Tests fail due to a bug in either pylibmc or libmemcached (detailts at pylibmc-issue:

(sprint)mbdev001:tests basp$ python --settings=test_sqlite_cache cache.MemcachedCacheTests
Creating test database for alias 'default'...
Creating test database for alias 'other'...
ERROR: test_invalid_keys (regressiontests.cache.tests.MemcachedCacheTests)
Traceback (most recent call last):
  File "/Users/basp/dev/repos/django/tests/regressiontests/cache/", line 963, in tearDown
  File "/Users/basp/dev/envs/sprint/lib/python2.7/site-packages/django/core/cache/backends/", line 140, in clear
SomeErrors: error 19 from flush_all: SUCCESS

Ran 35 tests in 4.085s

FAILED (errors=1)
Destroying test database for alias 'default'...
Destroying test database for alias 'other'...


    'default': {
        'BACKEND': 'django.core.cache.backends.memcached.PyLibMCCache',
        'LOCATION': '',

Change History (1)

comment:1 Changed 3 years ago by jacob

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to invalid
  • Status changed from new to closed

It seems to me that this is a bug with pylibmc, right? I'm not sure Django could do anything here. I'm going to close this, please feel free to reopen if the bug's actually in Django.

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