You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Simo proposed that we crate a unit test that would corrupt the memcache and then simulate a lookup to see if the sssd_nss process or the client side memcache code survives the corrupt cache. I think this fits nicely with out other 1.12 plans.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/2045
Simo proposed that we crate a unit test that would corrupt the memcache and then simulate a lookup to see if the sssd_nss process or the client side memcache code survives the corrupt cache. I think this fits nicely with out other 1.12 plans.
Comments
Comment from mzidek at 2013-08-12 20:34:14
Fields changed
owner: somebody => mzidek
Comment from jhrozek at 2013-08-14 22:25:16
Fields changed
patch: 0 => 1
Comment from sbose at 2013-08-15 15:05:12
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.12 beta
patch: 1 => 0
Comment from dpal at 2013-09-12 16:40:53
Fields changed
rhbz: => 0
Comment from lslebodn at 2014-02-19 11:54:59
Fields changed
blocking: => #1923
Comment from jhrozek at 2014-05-30 15:53:51
Fields changed
milestone: SSSD 1.12 beta => SSSD 1.12.1
Comment from jhrozek at 2014-07-02 18:56:54
Fields changed
review: 0 => 1
Comment from mzidek at 2014-07-03 23:24:47
Fields changed
resolution: => invalid
status: new => closed
Comment from jhrozek at 2017-02-24 14:40:50
Metadata Update from @jhrozek:
The text was updated successfully, but these errors were encountered: