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
During review of patches for #2730, we noticed the tests should use check_leaks_push/pop in the test fixtures to catch issues where memory was allocated on long-living contexts (like responder or event context).
For the time being, filing into 1.14 beta, we will decide if there is still time to use cache_req in 1.14 or whether we need to move that enhancement to 1.15..
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/2869
During review of patches for #2730, we noticed the tests should use check_leaks_push/pop in the test fixtures to catch issues where memory was allocated on long-living contexts (like responder or event context).
Comments
Comment from jhrozek at 2015-11-18 09:52:08
Triage notes - this should be a prerequisite for using cache_req in responders (#1126) which is currently 1.14.
Comment from jhrozek at 2015-11-19 15:42:00
For the time being, filing into 1.14 beta, we will decide if there is still time to use cache_req in 1.14 or whether we need to move that enhancement to 1.15..
milestone: NEEDS_TRIAGE => SSSD 1.14 beta
Comment from jhrozek at 2015-12-03 22:15:04
Fields changed
rhbz: => 0
Comment from jhrozek at 2016-02-16 12:43:34
Pavel agreed on IRC to fix this ticket.
owner: somebody => pbrezina
Comment from pbrezina at 2016-02-16 12:44:44
Fields changed
status: new => assigned
Comment from pbrezina at 2016-02-18 14:51:22
Fields changed
patch: 0 => 1
Comment from jhrozek at 2016-03-14 17:53:45
Comment from jhrozek at 2016-06-20 11:37:57
Fields changed
milestone: SSSD 1.14 beta => SSSD 1.14 alpha
resolution: => fixed
status: assigned => closed
Comment from jhrozek at 2017-02-24 14:52:47
Metadata Update from @jhrozek:
The text was updated successfully, but these errors were encountered: