[Cvs-test-results] Nightly testing results for TRUNK (alpha Linux 2.2.20)

[cvstest]

Nightly test results for Mon Sep 26 22:34:28 PDT 2005
Linux usf-cf-alpha-linux-1 2.2.20 #2 Wed Mar 20 19:57:28 EST 2002 alpha unknown

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, try the command: `tail -f check.log' from another window.)
OK, all 3579 tests passed (10 test groups skipped).
/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, try the command: `tail -f check.log' from another window.)
PASS: client-19
** expected: 
cvs commit: Examining \.
cvs \[commit aborted\]: `Redirect' loop detected\.  Server misconfiguration?
** got: 
cvs commit: Examining .
cat: Memory exhausted
cat: Memory exhausted
cat: Memory exhausted
cat: Memory exhausted
cat: Memory exhausted
cat: Memory exhausted
cat: error while loading shared libraries: libc.so.6.1: failed to map segment 
from shared object: Cannot allocate memory
cat: error while loading shared libraries: libc.so.6.1: failed to map segment 
from shared object: Cannot allocate memory
cat: error while loading shared libraries: libc.so.6.1: failed to map segment 
from shared object: Cannot allocate memory
cvs [commit aborted]: memory exhausted
FAIL: client-20
/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, try the command: `tail -f check.log' from another window.)
OK, all 3606 tests passed (2 test groups skipped).