[SSSD] Build error on Ubuntu 12.10

Jakub Hrozek jhrozek at redhat.com
Thu Apr 25 14:59:19 UTC 2013


On Thu, Apr 25, 2013 at 01:58:39PM +0200, linux wrote:
> On 2013-04-25 12:10, Jakub Hrozek wrote:
> >On Thu, Apr 25, 2013 at 09:24:22AM +0200, linux wrote:
> >>Hi,
> >>
> >>I'm trying to build sssd 1.9.5 on Ubuntu 12.10 and I got the
> >>following error:
> >>
> >>Running suite(s): sysdb
> >>99%: Checks: 800, Failures: 1, Errors: 1
> >>../src/tests/sysdb-tests.c:701:E:SYSDB
> >>Tests:test_sysdb_add_user:27000: (after this point) Test timeout
> >>expired
> >>../src/tests/sysdb-tests.c:854:F:SYSDB
> >>Tests:test_sysdb_getpwnam:27000: Invalid number of replies. Expected
> >>1, got 0
> >>FAIL: sysdb-tests
> >
> >Is this reproducable? We run the unit tests on each build
> >(including the
> >nigtlies) and it never failed for us.
> 
> No, now I get the following error:
> 
> Running suite(s): access_simple
> 80%: Checks: 10, Failures: 1, Errors: 1
> ../src/tests/simple_access-tests.c:198:S:group
> allow/deny:test_group_both_set:0: (after this point) Test timeout
> expired
> ../src/tests/simple_access-tests.c:151:S:group
> allow/deny:test_group_case:0: Could not add private group
> FAIL: simple_access-tests
> 
> maybe my desktop is too overloaded which causes the timeout. I'll
> stop the VMs running and try again.

If it's an intermittent problem, then it's quite possible that high load
is the cause.

Maybe setting CK_DEFAULT_TIMEOUT=$SOME_LARGE_VALUE might get around the
problem:
http://check.sourceforge.net/doc/check_html/check_4.html#Test-Timeouts

> My goal is to build a debian package for Ubuntu and Debian
> squeeze/wheezy.
> 

I know that the Ubuntu maintainer, Timo Aaltonen has been tracking the
SSSD upstream quite closely, is there anything missing in the packages
he builds?

> >
> >Can you step the test_sysdb_add_user with a gdb ?
> 
> I'm not so familiar with C programming and debugging, but will do
> that if my workstation is not the cause for the failure.

If the problem doesn't always happen and your workstation is quite
loaded, then I think it's really the timeout.



More information about the sssd-devel mailing list