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

[cvstest]

Nightly test results for Mon Nov 6 01:31:34 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.)
OK, all 3649 tests passed (11 test groups skipped and 1 test passed with 
warnings).
104.42user 215.39system 39:08.36elapsed 13%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (1major+8829982minor)pagefaults 0swaps

/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.)
FAIL: binfiles-sticky2
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [remotecheck] Error 1
Command exited with non-zero status 2
113.60user 221.74system 17:16.94elapsed 32%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+9039560minor)pagefaults 0swaps
PASS: binfiles-sticky1
cvs [commit aborted]: sign program exited via signal 11
exit status was 1
FAIL: binfiles-sticky2

/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).
224.05user 458.96system 59:42.58elapsed 19%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (6major+18769354minor)pagefaults 0swaps