Code

#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

Description

Tests fail due to a bug in either pylibmc or libmemcached (detailts at pylibmc-issue: https://github.com/lericson/pylibmc/issues/114)

(sprint)mbdev001:tests basp$ python runtests.py --settings=test_sqlite_cache cache.MemcachedCacheTests
Creating test database for alias 'default'...
Creating test database for alias 'other'...
...........................E.......
======================================================================
ERROR: test_invalid_keys (regressiontests.cache.tests.MemcachedCacheTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/basp/dev/repos/django/tests/regressiontests/cache/tests.py", line 963, in tearDown
    self.cache.clear()
  File "/Users/basp/dev/envs/sprint/lib/python2.7/site-packages/django/core/cache/backends/memcached.py", line 140, in clear
    self._cache.flush_all()
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'...

settings:

CACHES = {
    'default': {
        'BACKEND': 'django.core.cache.backends.memcached.PyLibMCCache',
        'LOCATION': '127.0.0.1:11211',
    }
}

Attachments (0)

Change History (1)

comment:1 Changed 17 months 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.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.