Learn more about these different git repos.
Other Git URLs
Tried to enable check/mocka for 1.12.4 but it fails:
dh_auto_test: make -j8 check returned exit code 2 =================================== sssd 1.12.4: ./test-suite.log =================================== # TOTAL: 56 # PASS: 54 # SKIP: 0 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: sbus_tests ================ Running suite(s): sbus 20%: Checks: 5, Failures: 4, Errors: 0 ../src/tests/sbus_tests.c:218:F:tests:test_raw_handler:0: Assertion 'reply != ((void *)0)' failed ../src/tests/sbus_tests.c:275:F:tests:test_request_parse_ok:0: Assertion 'reply != ((void *)0)' failed ../src/tests/sbus_tests.c:303:F:tests:test_request_parse_bad_args:0: Assertion 'dbus_error_has_name(&error, "org.freedesktop.DBus.Error.InvalidArgs")' failed ../src/tests/sbus_tests.c:328:F:tests:test_introspection:0: Assertion 'reply != ((void *)0)' failed ../src/tests/sbus_tests.c:365:P:tests:test_sbus_new_error:0: Passed FAIL: sbus_codegen_tests ======================== Running suite(s): sbus_codegen 60%: Checks: 10, Failures: 4, Errors: 0 ../src/tests/sbus_codegen_tests.c:78:P:defs:test_interfaces:0: Passed ../src/tests/sbus_codegen_tests.c:102:P:defs:test_methods:0: Passed ../src/tests/sbus_codegen_tests.c:114:P:defs:test_properties:0: Passed ../src/tests/sbus_codegen_tests.c:131:P:defs:test_signals:0: Passed ../src/tests/sbus_codegen_tests.c:192:P:defs:test_vtable:0: Passed ../src/tests/sbus_codegen_tests.c:206:P:defs:test_constants:0: Passed ../src/tests/sbus_codegen_tests.c:671:F:handler:test_marshal_basic_types:0: Assertion 'reply != ((void *)0)' failed ../src/tests/sbus_codegen_tests.c:797:F:handler:test_get_basic_types:0: Assertion 'reply != ((void *)0)' failed ../src/tests/sbus_codegen_tests.c:1308:F:handler:test_getall_basic_types:0: Assertion 'reply != ((void *)0)' failed ../src/tests/sbus_codegen_tests.c:948:F:handler:test_get_basic_array_types:0: Assertion 'reply != ((void *)0)' failed
Lukas is our debian expert..
owner: somebody => lslebodn
If the tests cannot be made working on debian for one reason or other, we can disable them with a config-time option (or debian can have a downstream patch).
milestone: NEEDS_TRIAGE => SSSD Deferred
Fields changed
rhbz: => 0
description: Tried to enable check/mocka for 1.12.4 but it fails:
.. contents:: :depth: 2
Running suite(s): sbus 20%: Checks: 5, Failures: 4, Errors: 0 ../src/tests/sbus_tests.c:218:F:tests:test_raw_handler:0: Assertion 'reply != ((void )0)' failed ../src/tests/sbus_tests.c:275:F:tests:test_request_parse_ok:0: Assertion 'reply != ((void )0)' failed ../src/tests/sbus_tests.c:303:F:tests:test_request_parse_bad_args:0: Assertion 'dbus_error_has_name(&error, "org.freedesktop.DBus.Error.InvalidArgs")' failed ../src/tests/sbus_tests.c:328:F:tests:test_introspection:0: Assertion 'reply != ((void *)0)' failed ../src/tests/sbus_tests.c:365:P:tests:test_sbus_new_error:0: Passed
Running suite(s): sbus_codegen 60%: Checks: 10, Failures: 4, Errors: 0 ../src/tests/sbus_codegen_tests.c:78:P:defs:test_interfaces:0: Passed ../src/tests/sbus_codegen_tests.c:102:P:defs:test_methods:0: Passed ../src/tests/sbus_codegen_tests.c:114:P:defs:test_properties:0: Passed ../src/tests/sbus_codegen_tests.c:131:P:defs:test_signals:0: Passed ../src/tests/sbus_codegen_tests.c:192:P:defs:test_vtable:0: Passed ../src/tests/sbus_codegen_tests.c:206:P:defs:test_constants:0: Passed ../src/tests/sbus_codegen_tests.c:671:F:handler:test_marshal_basic_types:0: Assertion 'reply != ((void )0)' failed ../src/tests/sbus_codegen_tests.c:797:F:handler:test_get_basic_types:0: Assertion 'reply != ((void )0)' failed ../src/tests/sbus_codegen_tests.c:1308:F:handler:test_getall_basic_types:0: Assertion 'reply != ((void )0)' failed ../src/tests/sbus_codegen_tests.c:948:F:handler:test_get_basic_array_types:0: Assertion 'reply != ((void )0)' failed => Tried to enable check/mocka for 1.12.4 but it fails: {{{ dh_auto_test: make -j8 check returned exit code 2 =================================== sssd 1.12.4: ./test-suite.log ===================================
Running suite(s): sbus_codegen 60%: Checks: 10, Failures: 4, Errors: 0 ../src/tests/sbus_codegen_tests.c:78:P:defs:test_interfaces:0: Passed ../src/tests/sbus_codegen_tests.c:102:P:defs:test_methods:0: Passed ../src/tests/sbus_codegen_tests.c:114:P:defs:test_properties:0: Passed ../src/tests/sbus_codegen_tests.c:131:P:defs:test_signals:0: Passed ../src/tests/sbus_codegen_tests.c:192:P:defs:test_vtable:0: Passed ../src/tests/sbus_codegen_tests.c:206:P:defs:test_constants:0: Passed ../src/tests/sbus_codegen_tests.c:671:F:handler:test_marshal_basic_types:0: Assertion 'reply != ((void )0)' failed ../src/tests/sbus_codegen_tests.c:797:F:handler:test_get_basic_types:0: Assertion 'reply != ((void )0)' failed ../src/tests/sbus_codegen_tests.c:1308:F:handler:test_getall_basic_types:0: Assertion 'reply != ((void )0)' failed ../src/tests/sbus_codegen_tests.c:948:F:handler:test_get_basic_array_types:0: Assertion 'reply != ((void )0)' failed }}}
I was not able to reproduce failed sbus test. (different test failed in my case.
user@vm-066:~/deb_pkgs$ grep -E "FAIL|(: sbus)" sssd_1.12.4-1_amd64.build PASS: sbus-internal-tests FAIL: fail_over-tests PASS: sbus_tests PASS: sbus_codegen_tests # XFAIL: 0 # FAIL: 1 FAIL: fail_over-tests ../src/tests/fail_over-tests.c:138:P:FAIL_OVER Tests:test_fo_new_service:0: Passed ../src/tests/fail_over-tests.c:160:F:FAIL_OVER Tests:test_fo_resolve_service:0: ../src/tests/fail_over-tests.c:244: Expected return of 0, got 110 # XFAIL: 0 # FAIL: 1
Will it fail if test are run with make -j1?
BTW here is an output of failed failover test.
FAIL: fail_over-tests ===================== Running suite(s): fail_over (Wed Apr 22 16:24:57:970489 2015) [sssd] [fo_new_service] (0x0400): Creating new service 'ntp' (Wed Apr 22 16:24:57:970547 2015) [sssd] [fo_add_server_to_list] (0x0400): Inserted primary server 'localhost:20' to service 'http' (Wed Apr 22 16:24:57:970590 2015) [sssd] [fo_add_server_to_list] (0x0400): Inserted backup server '127.0.0.1:80' to service 'http' (Wed Apr 22 16:24:57:970625 2015) [sssd] [fo_add_server_to_list] (0x0400): Inserted backup server 'localhost:30' to service 'ldap' (Wed Apr 22 16:24:57:970656 2015) [sssd] [fo_add_server_to_list] (0x0400): Inserted primary server '127.0.0.1:389' to service 'ldap' (Wed Apr 22 16:24:57:970687 2015) [sssd] [fo_add_server_to_list] (0x0400): Server '127.0.0.1:389' for service 'ldap' is already present (Wed Apr 22 16:24:57:970729 2015) [sssd] [fo_add_server_to_list] (0x0400): Server '127.0.0.1:389' for service 'ldap' is already present (Wed Apr 22 16:24:57:970761 2015) [sssd] [fo_add_server_to_list] (0x0400): Inserted primary server '(no name):123' to service 'ntp' (Wed Apr 22 16:24:57:970796 2015) [sssd] [fo_resolve_service_send] (0x0100): Trying to resolve service 'http' (Wed Apr 22 16:24:57:970832 2015) [sssd] [get_server_status] (0x1000): Status of server 'localhost' is 'name not resolved' (Wed Apr 22 16:24:57:970862 2015) [sssd] [get_port_status] (0x1000): Port status of port 20 for server 'localhost' is 'neutral' (Wed Apr 22 16:24:57:970905 2015) [sssd] [fo_resolve_service_activate_timeout] (0x2000): Resolve timeout set to 0 seconds (Wed Apr 22 16:24:57:970928 2015) [sssd] [get_server_status] (0x1000): Status of server 'localhost' is 'name not resolved' (Wed Apr 22 16:24:57:970960 2015) [sssd] [resolv_is_address] (0x4000): [localhost] does not look like an IP address (Wed Apr 22 16:24:57:970984 2015) [sssd] [resolv_gethostbyname_step] (0x2000): Querying files (Wed Apr 22 16:24:57:971007 2015) [sssd] [resolv_gethostbyname_files_send] (0x0100): Trying to resolve A record of 'localhost' in files (Wed Apr 22 16:24:57:971057 2015) [sssd] [set_server_common_status] (0x0100): Marking server 'localhost' as 'resolving name' (Wed Apr 22 16:24:57:971118 2015) [sssd] [resolv_gethostbyname_step] (0x2000): Querying files (Wed Apr 22 16:24:57:971145 2015) [sssd] [resolv_gethostbyname_files_send] (0x0100): Trying to resolve AAAA record of 'localhost' in files (Wed Apr 22 16:24:57:971197 2015) [sssd] [resolv_gethostbyname_next] (0x0200): No more address families to retry (Wed Apr 22 16:24:57:971222 2015) [sssd] [resolv_gethostbyname_step] (0x2000): Querying DNS (Wed Apr 22 16:24:57:971285 2015) [sssd] [resolv_gethostbyname_dns_query] (0x0100): Trying to resolve A record of 'localhost' in DNS (Wed Apr 22 16:24:57:971316 2015) [sssd] [schedule_request_timeout] (0x2000): Scheduling a timeout of 5 seconds (Wed Apr 22 16:24:57:971347 2015) [sssd] [schedule_timeout_watcher] (0x2000): Scheduling DNS timeout watcher (Wed Apr 22 16:24:57:971520 2015) [sssd] [fo_resolve_service_timeout] (0x0080): Service resolving timeout reached 50%: Checks: 2, Failures: 1, Errors: 0 ../src/tests/fail_over-tests.c:138:P:FAIL_OVER Tests:test_fo_new_service:0: Passed ../src/tests/fail_over-tests.c:160:F:FAIL_OVER Tests:test_fo_resolve_service:0: ../src/tests/fail_over-tests.c:244: Expected return of 0, got 110
The file /etc/hosts was not available and thus localhost could not be resolved.
Metadata Update from @tjaalton: - Issue assigned to lslebodn - Issue set to the milestone: SSSD Patches welcome
I'm closing this since we have reimplemented sbus in SSSD 2.0 and we do not plan to work on this.
Metadata Update from @pbrezina: - Custom field design_review reset (from 0) - Custom field mark reset (from 0) - Custom field patch reset (from 0) - Custom field review reset (from 0) - Custom field testsupdated reset (from 0) - 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/3658
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.
Log in to comment on this ticket.