Glibc test suite fails

ReyJavikVI · 08-04-2009, 12:25 PM

In chapter 6.9 (LFS 6.4) the Glibc test suite fails three times:

Code:

[Lots of output...]
make[1]: Target `check' not remade because of errors.
make[1]: Leaving directory `/src/glibc-2.8-20080929'
make: *** [check] Error 2
root:/src/glibc-build# grep Error glibc-check-log
make[2]: [/src/glibc-build/posix/annexc.out] Error 1 (ignored)
make[2]: *** [/src/glibc-build/rt/tst-timer4.out] Error 1
make[1]: *** [rt/tests] Error 2
make: *** [check] Error 2

Can anyone help?

weibullguy · 08-04-2009, 03:04 PM

Obviously the glibc test suite ignored the annexc error and you should too. For the other error you can consult the logs http://www.linuxfromscratch.org/lfs/build-logs/. Maybe it's something the developers are aware of and have deemed non-critical. Otherwise, why don't you see what information the output file /src/glibc-build/rt/tst-timer4.out has?

ReyJavikVI · 08-04-2009, 03:55 PM

The dev's logs don't say anything about it. Here's the contents of rt/tst-timer4.out, maybe someone can help me make sense out of this.

Code:

clock_gettime returned timespec = { 1249404867, 504447523 }
clock_getres returned timespec = { 0, 1 }
*** timer sig2 invoked too soon: 1249404868.009876510 instead of expected 1249404868.009998979

The only thing I can understand is that some time-related function returned a couple of 1/10000s of a second less than expected. Or so it seems.

ProtoformX · 08-04-2009, 11:37 PM

Quote:

Originally Posted by ReyJavikVI

The dev's logs don't say anything about it. Here's the contents of rt/tst-timer4.out, maybe someone can help me make sense out of this.

Code:

clock_gettime returned timespec = { 1249404867, 504447523 }
clock_getres returned timespec = { 0, 1 }
*** timer sig2 invoked too soon: 1249404868.009876510 instead of expected 1249404868.009998979

The only thing I can understand is that some time-related function returned a couple of 1/10000s of a second less than expected. Or so it seems.

Ignore tst-timer errors the previous books note that some machines have these problems and this shouldn't be a serious problem.