Wojciech Giel wrote:
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of lfs-support digest..."
Please follow that advice. It makes life easier for people to see what
the mail is about before they open it :-)
>
>From: "Brandon Peirce"
>
>Wojciech Giel wrote:
>
>
>>Hi
>>I'm compiling LFS 6.2.
>>I get this result of check test of glibc in 6.9 chapter
>>
>>make[2]: *** [/sources/glibc-build/rt/tst-mqueue5.out] Error 1
>>
>
>Maybe you are lucky and it just timed out. Try
> grep -A 1 '^Timed out' glibc-check-log
>
>If you get two lines of output:
> Timed out: Killed the child process
> make[2]: *** [/sources/glibc-build/rt/tst-mqueue5.out] Error 1
>then that's the answer.
>
>Otherwise, try to check the contents of that tst-mqueue5.out file.
>It's contents should be the output of the test case.
>
i have two processors 400 Mhz i this box. I compiled glibc once again
with MAKEOPTS="-j5" and i only get
(ignored) failure in the posix/annexc test which is acceptable
it seems as if it was problem with slow processor. sorry for my english.
does time out mean slow processor in other words ? :-)
Hmmm, a dual processor 400MHz... Compaq AP400 professional worstation
maybe? I worked a lot with those in my former company :)
The person who writes the test case expects it to finish in a certain time,
e.g. 10 seconds. It is made so that if the test is not finished in that
time,
then it is cancelled (stopped). That is called a "time out" and the test
fails.
If you run on a 400MHz box, it is very likely that you will get a few time
outs,
especially if your box is also busy with something else.
However, I think it is not a very good idea to use MAKEOPTS="-j5" for the
test suite (although it seems to work ok the first time for you). The Glibc
Makefiles use a specific variable PARALLELMFLAGS which is specifically set
to -j1 for the testsuite IIRC. You should not cause any damage by running
parallel make for the test suite, but it might give unexpected failures or
even
crash if some commands are executed in a random sequence.
For Glibc testsuite, the correct solution is to use TIMEOUTFACTOR.
Try something like
make TIMEOUTFACTOR=5 check
This will make all the time outs 5 times longer, e.g. a test that timed out
in 10
seconds before will now be allowed to run for 50 seconds before it is
stopped, and probably it will pass after 20 seconds!
However, I think your previous (lucky?) result with MAKEOPTS="-j5" shows
it is safe to continue. You don't need to rerun the test with TIMEOUTFACTOR
unless you are interested.
Regards,
Brandon
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
