[Cvs-test-results] Testing results for cvs-nightly (ppc64 Linux 2.6.5-7.97-pseries64)

[cvstest]

Nightly test results for Wed Aug 16 22:31:39 PDT 2006
Linux openpower-linux1 2.6.5-7.97-pseries64 #1 SMP Fri Jul 2 14:21:59 UTC 2004 
ppc64 ppc64 ppc64 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
17.67user 46.61system 10:52.84elapsed 9%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (10major+3478742minor)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
28.64user 70.43system 14:14.46elapsed 11%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+5306712minor)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
36.60user 90.63system 25:18.66elapsed 8%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (1major+7367720minor)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