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

[cvstest]

Nightly test results for Sat Nov 18 01:31:33 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.23user 219.58system 33:33.37elapsed 16%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (4major+8838060minor)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-noredirect-11
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [remotecheck] Error 1
Command exited with non-zero status 2
178.93user 353.43system 39:01.61elapsed 22%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (5major+14393763minor)pagefaults 0swaps
PASS: writeproxy-noredirect-10
** expected: 
U file1
** got: 
FAIL: writeproxy-noredirect-11

/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.39user 457.24system 58:54.43elapsed 19%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+18757786minor)pagefaults 0swaps