#2730 responder_cache_req-tests failed
Closed: Fixed Opened by lslebodn.

[ RUN      ] test_groups_by_filter_multiple_domains_valid
0x1 != 0x2
/var/lib/jenkins/workspace/ci/label/rhel7/src/tests/cmocka/test_responder_cache_req.c:2054: error: Failure!
[  FAILED  ] test_groups_by_filter_multiple_domains_valid

http://sssd-ci.duckdns.org/logs/job/19/09/rhel7/ci-build-debug/responder_cache_req-tests.log


Fields changed

owner: somebody => pcech

Fields changed

rhbz: => 0

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13.2

Fields changed

status: new => assigned

The problematic tests were removed in bdf422fde0fd6b40b3412bad3b200f8fd7ea8693

We would like to release the 1.13.2 tarball soon and this ticket is not a release blocker, therefore I'm moving it out of 1.13.2 into 1.13.3

milestone: SSSD 1.13.2 => SSSD 1.13.3
priority: major => minor

Fields changed

patch: 0 => 1

master:
- 16212bbb2aaa55d0587515e72c0018479ae51be9
- 5928fcbb57b92bfd18ad15aaaf4a5e1ab8dabe61
- fe6dd669d1e8606862879127f92c177bb7fdc1bd
- a6a5a08a357d2adbb653b81bacc602ca3543c4c4
- 6ae53d7b54ec2ece9fb51ed92c097f5ba8f9d849
- c4d4fe1603420fe8f3d256a3a446974699563ff3
- b0e8c1802557645e2ff6a88c54c520b0f0ff9ebb
- da79bee1472a06b89be2df903fb0bd8ce600c610
and sssd-1-13:
- 87a8f263e90264b826a0e968693ad3f285039687
- f4c7c9268b120fd3f70493c52a61a3a9857b3bff
- 56c7cb8682ef75555ccf8e2571bc3b394fab2659
- a6c3dba7e685a53502e30c76185500224675d608
- b87363f82d941e76389415af55656ba3785b912d
- 3d135f299e5fa8f4a37756930cc4924896387e26
- b6dd72c59f52fd6879091216e07c056ff72908b7
- 73519a95291066464f29bb2ee060f404b279f838

milestone: SSSD 1.13.3 => SSSD 1.13.2
resolution: => fixed
status: assigned => closed

Metadata Update from @lslebodn:
- Issue assigned to pcech
- Issue set to the milestone: SSSD 1.13.2

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/3771

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.

Metadata