Learn more about these different git repos.
Other Git URLs
I can reproduce it on my machine. (Maybe I am the only one.)
There is a part of log:
(Thu Aug 20 07:40:49:577840 2015) [sssd] [test_multidom_suite_cleanup] (0x0020): Could not delete the test config ldb file : (Not a directory)
(Thu Aug 20 07:40:49:577887 2015) [sssd] [test_multidom_suite_cleanup] (0x0020): Could not delete the test domain ldb file : (Not a directory)
(Thu Aug 20 07:40:49:577899 2015) [sssd] [test_multidom_suite_cleanup] (0x0020): Could not delete the test dir (20) (Not a directory)
[==========] Running 1 test(s).
[ RUN ] test_id_cleanup_exp_group
(Thu Aug 20 07:40:49:578773 2015) [sssd] [ldb] (0x0020): Unable to open tdb 'test_ldap_id_cleanup/tests_conf.ldb': Not a directory
(Thu Aug 20 07:40:49:578786 2015) [sssd] [ldb] (0x0020): Failed to connect to 'test_ldap_id_cleanup/tests_conf.ldb' with backend 'tdb': Unable to open tdb 'test_ldap_id_cleanup/tests_conf.ldb': Not a directory
(Thu Aug 20 07:40:49:578791 2015) [sssd] [confdb_init] (0x0010): Unable to open config database [test_ldap_id_cleanup/tests_conf.ldb]
Could not run the test - check test fixtures
[ ERROR ] test_id_cleanup_exp_group
[==========] 1 test(s) run.
[ PASSED ] 0 test(s).
FAIL test_ldap_id_cleanup (exit status: 1)
I hit this bug as well.
Unfortunately, I cannot effort to spend time with fixing totally broken patch which I rejected. I will locally maintain patch which disable this test until it will be fixed in upstream. The author of patch should have enough knowledge about his test; therefore assigning this ticket to him.
owner: somebody => preichl
patch: 0 => 1
milestone: NEEDS_TRIAGE => SSSD 1.13.1
resolution: => fixed
status: new => closed
rhbz: => 0
Metadata Update from @pcech:
- Issue assigned to preichl
- Issue set to the milestone: SSSD 1.13.1
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:
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.
to comment on this ticket.