[Cvs-test-results] Testing results for cvs-nightly (alpha Linux 2.2.20)

[cvstest]

Nightly test results for Sat May 6 22:31:24 PDT 2006
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.)
FAIL: basica-o7
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [localcheck] Error 1
Command exited with non-zero status 2
2.12user 2.31system 0:17.54elapsed 25%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (66623major+37295minor)pagefaults 0swaps
PASS: basica-o6a

RCS file: 
/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/cvsroot/first-dir/sdir/ssdir/ssfile,v
Working file: ssfile
head: 3.1
branch:
locks: strict
access list:
keyword substitution: kv
total revisions: 3;     selected revisions: 3
description:
----------------------------
revision 3.1
date: 2006-05-06 22:34:34 -0700;  author: derekrprice;  state: Exp;  lines: +0 
-0;  commitid: paBsWO9XLnj293wr;
cvs [log aborted]: received abort signal
exit status was 1
FAIL: basica-o7

/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.)
FAIL: basica-o7
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [remotecheck] Error 1
Command exited with non-zero status 2
2.59user 2.93system 0:19.44elapsed 28%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (88928major+48250minor)pagefaults 0swaps
PASS: basica-o6a

RCS file: 
/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/cvsroot/first-dir/sdir/ssdir/ssfile,v
Working file: ssfile
head: 3.1
branch:
locks: strict
access list:
keyword substitution: kv
total revisions: 3;     selected revisions: 3
description:
----------------------------
revision 3.1
date: 2006-05-06 22:34:53 -0700;  author: derekrprice;  state: Exp;  lines: +0 
-0;  commitid: XPTU1v8ndp1993wr;
cvs [log aborted]: received abort signal
exit status was 1
FAIL: basica-o7

/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.)
FAIL: basica-o7
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [proxycheck] Error 1
Command exited with non-zero status 2
3.43user 5.96system 0:43.76elapsed 21%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (128809major+64717minor)pagefaults 0swaps
PASS: basica-o6a

RCS file: 
/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/cvsroot/first-dir/sdir/ssdir/ssfile,v
Working file: ssfile
head: 3.1
branch:
locks: strict
access list:
keyword substitution: kv
total revisions: 3;     selected revisions: 3
description:
----------------------------
revision 3.1
date: 2006-05-06 22:35:26 -0700;  author: derekrprice;  state: Exp;  lines: +0 
-0;  commitid: 9jN06LicuQBk93wr;
cvs [log aborted]: received abort signal
exit status was 1
FAIL: basica-o7