[SSSD] resolv-tests failing
Jakub Hrozek
jhrozek at redhat.com
Wed Apr 10 19:46:11 UTC 2013
On Wed, Apr 10, 2013 at 03:34:39PM -0400, Yassir Elley wrote:
> I did a fresh "git clone" from master earlier today on a Fedora 19 VM. The source code builds fine, but "make check" is reporting that a test named "resolv-tests" is failing.
>
> Regards,
> Yassir.
>
> ===================================
> sssd 1.9.92: ./test-suite.log
> ===================================
>
> # TOTAL: 24
> # PASS: 23
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
>
> .. contents:: :depth: 2
>
> FAIL: resolv-tests
> ==================
>
> Network tests disabled. Rerun with the "-n" option to run the full suite of tests
> Running suite(s): resolv
> Leak report for ../src/tests/resolv-tests.c:719:
> full talloc report on 'struct resolv_test_ctx' (total 664 bytes in 11 blocks)
> struct resolv_ctx contains 352 bytes in 6 blocks (ref 0) 0x12a81c0
> struct tevent_timer contains 80 bytes in 1 blocks (ref 0) 0x12a8e30
> struct fd_watch contains 128 bytes in 2 blocks (ref 0) 0x12a8fc0
> struct tevent_fd contains 88 bytes in 1 blocks (ref 0) 0x12a9050
> struct resolv_request contains 104 bytes in 2 blocks (ref 0) 0x12a8db0
> struct tevent_timer contains 80 bytes in 1 blocks (ref 0) 0x12a8cf0
> struct tevent_context contains 280 bytes in 4 blocks (ref 0) 0x12a7ef0
> struct epoll_event_context contains 40 bytes in 1 blocks (ref 0) 0x12a8130
> struct std_event_glue contains 112 bytes in 2 blocks (ref 0) 0x12a7fe0
> struct tevent_ops contains 80 bytes in 1 blocks (ref 0) 0x12a8070
> 80%: Checks: 5, Failures: 1, Errors: 0
> ../src/tests/common_check.c:54:F:RESOLV Tests:test_resolv_free_req:0: ../src/tests/resolv-tests.c:719: memory leaks detected, 312 bytes still allocated
Hey Yassir,
The unit tests work OK here on a F-18 machine..
Did you build the SSSD in-tree or with something like "make rpms" or
mock? Do you know what was in /etc/resolv.conf when the test failed?
It's possible the tests don't cope well with the particular environment
(still a bug, though)
More information about the sssd-devel
mailing list