#19914: MemcachedCacheTests failing on pylibmc
-------------------------------------+-------------------------------------
     Reporter:  bpeschier            |                    Owner:  nobody
         Type:  Bug                  |                   Status:  closed
    Component:  Core (Cache system)  |                  Version:  master
     Severity:  Normal               |               Resolution:  invalid
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by edmorley):

 * cc: emorley@… (added)


Comment:

 This still reproduces with pylibmc 1.5.1 and libmemcached 1.0.8 (the
 latest for Ubuntu 14.04).

 The pylibmc issue was closed as "expected" - perhaps we should just skip
 these tests on pylibmc?

 {{{
 test_incr_version (cache.tests.MemcachedCacheTests) ... ok
 test_invalid_keys (cache.tests.MemcachedCacheTests) ... ERROR
 test_long_timeout (cache.tests.MemcachedCacheTests) ... ERROR
 ERROR
 test_memcached_deletes_key_on_failed_set (cache.tests.MemcachedCacheTests)
 ... python: libmemcached/storage.cc:341: memcached_return_t
 memcached_send_ascii(memcached_st*, memcached_server_write_instance_st,
 const char*, size_t, const char*, size_t, time_t, uint32_t, uint64_t,
 bool, bool, memcached_storage_action_t): Assertion `memcached_failed(rc)'
 failed.
 Aborted
 }}}

 If not, then I think the ticket's resolution is best 'wontfix' rather than
 'invalid' - though I mainly just wanted to update this ticket now to have
 something to point at when my PR fails some of the tests, to help prove
 that the failures were pre-existing.

--
Ticket URL: <https://code.djangoproject.com/ticket/19914#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.66b6338a0a0e69e568f6af1977eb6646%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to