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

[cvstest]

Nightly test results for Tue Nov 28 01:31:29 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).
105.05user 220.09system 32:32.41elapsed 16%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (4major+8838981minor)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: writeproxy-ssh-noredirect-4
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [remotecheck] Error 1
Command exited with non-zero status 2
184.45user 358.63system 40:11.28elapsed 22%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (4major+14472528minor)pagefaults 0swaps
PASS: writeproxy-ssh-noredirect-3
cvs commit: use `cvs add' to create an entry for `file1'
cvs [commit aborted]: correct above errors first!
exit status was 1
FAIL: writeproxy-ssh-noredirect-4

/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).
227.73user 461.87system 1:07:55elapsed 16%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+18761236minor)pagefaults 0swaps