[Cvs-test-results] Testing results for cvs-nightly (x86_64 Linux 2.6.9-1.667smp)

[cvstest]

Nightly test results for Fri Aug 18 22:31:27 PDT 2006
Linux amd64-linux1.sourceforge.net 2.6.9-1.667smp #1 SMP Tue Nov 2 15:09:11 EST 
2004 x86_64 x86_64 x86_64 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
15.19user 37.77system 10:34.91elapsed 8%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (2major+3966988minor)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
25.42user 60.60system 14:03.17elapsed 10%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+6161297minor)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
32.19user 78.70system 24:48.15elapsed 7%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+8369693minor)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