Learn more about these different git repos.
Other Git URLs
Tools like sss_cache are relatively easy to test, make check should have additional tests that set up data in the ldb cache and then run our tools forking them off, finally check the data in teh cache reflect the outcome we expect.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.10 beta priority: major => minor rhbz: => 0 selected: => Want type: defect => task
Not critical for beta and only affects unit tests. Can be done in 1.10 proper.
milestone: SSSD 1.10 beta => SSSD 1.10.0 review: => 0
milestone: SSSD 1.10.0 => SSSD 1.10.1
I doubt this is going to make 1.10.1. I would prefer to introduce tests for the tools along with improving the test coverage during the F-20 cycle.
changelog: => milestone: SSSD 1.10.1 => NEEDS_TRIAGE
milestone: NEEDS_TRIAGE => Interim Bucket
milestone: Interim Bucket => SSSD 1.12 beta
blocking: => #1923
review: 0 => 1
milestone: SSSD 1.12 beta => SSSD 1.13 beta
mark: => 0
owner: somebody => preichl
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
Mass-moving tickets not planned for the next two releases.
Please reply with a comment if you disagree about the move..
milestone: SSSD 1.13 backlog => SSSD 1.15 beta
Metadata Update from @simo: - Issue assigned to preichl - Issue marked as blocked by: #1923 - Issue set to the milestone: SSSD Future releases (no date set yet)
Metadata Update from @thalman: - Custom field blocking reset (from #1923) - Custom field design_review reset (from 0) - Custom field mark reset (from 0) - Custom field patch reset (from 0) - Custom field review adjusted to on (was: 1) - Custom field testsupdated reset (from 0) - Issue close_status updated to: None - Issue tagged with: Canditate to close
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)
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/2795
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.