#2055 Create unit tests for the memory cache
Closed: wontfix 4 years ago by pbrezina. Opened 10 years ago by jhrozek.

The memcache has seen quite a few patches lately and in general is a critical component, so we should add unit tests. Lukas came up with helper functions to exercise the memcache, which could be used as a starting point


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12 beta
rhbz: => 0

Fields changed

blocking: => #1923
owner: somebody => lslebodn

Fields changed

milestone: SSSD 1.12 beta => SSSD 1.12.1

Mass-moving all tickets that didn't make 1.12.1 into 1.12.2

milestone: SSSD 1.12.1 => SSSD 1.12.2

We need to do a release as requested by downstream. Moving tickets that are not fixed already or very close to acking to 1.12.3

milestone: SSSD 1.12.2 => SSSD 1.12.3

It makes sense to write the unit tests now instead of moving them to a later release again, but the tickets in 1.12.3 should be more focused at this point. Moving to 1.12.4

mark: => 0
milestone: SSSD 1.12.3 => SSSD 1.12.4

Fields changed

milestone: SSSD 1.12.4 => SSSD Deferred

I suggest we close this ticket because we now have integration tests for memory cache.

review: 0 => 1
sensitive: => 0

Fields changed

resolution: => invalid
status: new => closed

Integration test cannot cover all weird corner cases.

resolution: invalid =>
status: closed => reopened

Metadata Update from @jhrozek:
- Issue assigned to lslebodn
- Issue marked as blocked by: #1923
- Issue set to the milestone: SSSD Patches welcome

7 years ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

4 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/3097

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata