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

[cvstest]

Nightly test results for Tue Dec 19 22:39:04 PST 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, use the -v option or 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
8.29user 5.02system 0:23.84elapsed 55%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (68332major+38282minor)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-12-19 22:43:39 -0800;  author: derekrprice;  state: Exp;  lines: +0 
-0;  commitid: hkt5FKjYg1BleeZr;
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, use the -v option or 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
9.41user 5.83system 0:25.42elapsed 59%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (90915major+49676minor)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-12-19 22:44:05 -0800;  author: derekrprice;  state: Exp;  lines: +0 
-0;  commitid: ztm9OMOMpfMueeZr;
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, use the -v option or 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
11.81user 9.93system 0:55.78elapsed 38%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (131296major+66214minor)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-12-19 22:44:50 -0800;  author: derekrprice;  state: Exp;  lines: +0 
-0;  commitid: MNS1nS4xuuHKeeZr;
cvs [log aborted]: received abort signal
exit status was 1
FAIL: basica-o7