[Cvs-test-results] Testing results for cvs-nightly (i686 Linux 2.6.10-1.771_FC2smp)

[cvstest]

Nightly test results for Thu Aug 17 22:31:31 PDT 2006
Linux x86-linux2.cf.sourceforge.net 2.6.10-1.771_FC2smp #1 SMP Mon Mar 28 
01:10:51 EST 2005 i686 i686 i386 GNU/Linux

Please send questions/comments to address@hidden

/bin/sh /home/users/d/de/derekrprice/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: close-stdout-3
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [localcheck] Error 1
Command exited with non-zero status 2
32.22user 71.45system 10:48.08elapsed 15%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (2major+3134324minor)pagefaults 0swaps
PASS: close-stdout-2
** expected: 
cvs \[update aborted\]: write error.*
** got: 
cvs update: write error
FAIL: close-stdout-3

/bin/sh /home/users/d/de/derekrprice/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: close-stdout-3
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [remotecheck] Error 1
Command exited with non-zero status 2
57.90user 111.99system 14:24.77elapsed 19%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+4951949minor)pagefaults 0swaps
PASS: close-stdout-2
** expected: 
cvs \[update aborted\]: write error.*
** got: 
cvs update: write error: No space left on device
FAIL: close-stdout-3

/bin/sh /home/users/d/de/derekrprice/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.)
FAIL: close-stdout-3
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [proxycheck] Error 1
Command exited with non-zero status 2
75.14user 158.32system 26:36.40elapsed 14%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (3major+6858857minor)pagefaults 0swaps
PASS: close-stdout-2
** expected: 
cvs \[update aborted\]: write error.*
** got: 
cvs update: write error: No space left on device
FAIL: close-stdout-3