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

[cvstest]

Nightly test results for Sat Feb 17 01:30:22 EST 2007
Linux courage.ximbiot.com 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 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: toplevel-4
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [localcheck] Error 1
Command exited with non-zero status 2
56.92user 115.64system 1:23:08elapsed 3%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (15major+4614158minor)pagefaults 0swaps
PASS: toplevel-3
/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/cvsroot/top-dir/file1,v  <--  
file1
cvs [commit aborted]: sign program exited via signal 11
exit status was 1
FAIL: toplevel-4

/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 5 tests passed with 
warnings).
187.57user 340.73system 3:38:16elapsed 4%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (56major+14559818minor)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).
222.12user 431.13system 5:15:11elapsed 3%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (11major+18791279minor)pagefaults 0swaps