[Cvs-test-results] Testing results for cvs-nightly (i686 Linux 2.6.18-1.2200.fc5)

[cvstest]

Nightly test results for Sat Nov 25 01:31:30 EST 2006
Linux courage.ximbiot.com 2.6.18-1.2200.fc5 #1 Sat Oct 14 16:59:26 EDT 2006 
i686 i686 i386 GNU/Linux

Please send questions/comments to address@hidden

/bin/sh /mnt/nethome/cvstest/cvs-nightly/src/sanity.sh `pwd`/cvs
This test should produce no other output than this message, and a final "OK".
(Note that the test can take an hour or more to run and periodically stops
for as long as one minute.  Do not assume there is a problem just because
nothing seems to happen for a long time.  If you cannot live without
running status, use the -v option or try the command:
`tail -f check.log' from another window.)
FAIL: tag8k-5
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [localcheck] Error 1
Command exited with non-zero status 2
93.06user 196.09system 36:08.02elapsed 13%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (4major+7908596minor)pagefaults 0swaps
PASS: tag8k-4
** expected: 

** got: 
cvs commit: [07:13:09] waiting for cvstest's lock in 
/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/cvsroot/x
cvs commit: [07:13:39] obtained lock in 
/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/cvsroot/x
FAIL: tag8k-5

/bin/sh /mnt/nethome/cvstest/cvs-nightly/src/sanity.sh -r `pwd`/cvs
This test should produce no other output than this message, and a final "OK".
(Note that the test can take an hour or more to run and periodically stops
for as long as one minute.  Do not assume there is a problem just because
nothing seems to happen for a long time.  If you cannot live without
running status, use the -v option or try the command:
`tail -f check.log' from another window.)
OK, all 3858 tests passed (1 test group skipped and 6 tests passed with 
warnings).
184.57user 359.15system 39:53.09elapsed 22%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (8major+14555294minor)pagefaults 0swaps

/bin/sh /mnt/nethome/cvstest/cvs-nightly/src/sanity.sh -p `pwd`/cvs
This test should produce no other output than this message, and a final "OK".
(Note that the test can take an hour or more to run and periodically stops
for as long as one minute.  Do not assume there is a problem just because
nothing seems to happen for a long time.  If you cannot live without
running status, use the -v option or try the command:
`tail -f check.log' from another window.)
IO error encountered -- skipping file deletion
OK, all 3711 tests passed (2 test groups skipped and 5 tests passed with 
warnings).
226.35user 459.84system 59:34.29elapsed 19%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+18769678minor)pagefaults 0swaps