cvs-test-results
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: cvstest
Subject: [Cvs-test-results] Testing results for cvs-nightly (alpha Linux 2.2.20)
Date: Tue, 4 Jul 2006 01:48:59 -0400

Nightly test results for Mon Jul 3 22:31:33 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, 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
2.25user 2.28system 0:39.50elapsed 11%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (68005major+38890minor)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-07-03 22:46:25 -0700;  author: derekrprice;  state: Exp;  lines: +0 
-0;  commitid: 8IN6dU9LUaHvlvDr;
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-5
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [remotecheck] Error 1
Command exited with non-zero status 2
1.61user 1.36system 0:18.34elapsed 16%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (37224major+23064minor)pagefaults 0swaps
PASS: basica-4a
/tmp/build-cvs-nightly-cvs-nightly/cvs-sanity/cvsroot/first-dir/sdir/ssdir/ssfile,v
  <--  sdir/ssdir/ssfile
cvs [commit aborted]: memory exhausted
exit status was 1
FAIL: basica-5

/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: proxy-init-2
*** Please see the `TESTS' and `check.log' files for more information.
make: *** [proxycheck] Error 1
Command exited with non-zero status 2
1.32user 1.90system 0:18.40elapsed 17%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (30315major+17651minor)pagefaults 0swaps
PASS: proxy-init-1
cvs [commit aborted]: memory exhausted
exit status was 1
FAIL: proxy-init-2




reply via email to

[Prev in Thread] Current Thread [Next in Thread]