[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Cvs-test-results] Nightly testing results for signed-commits4 (alpha Li
From: |
cvstest |
Subject: |
[Cvs-test-results] Nightly testing results for signed-commits4 (alpha Linux 2.2.20) |
Date: |
Sun, 16 Apr 2006 06:06:27 -0400 |
Nightly test results for Sun Apr 16 02:22:43 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-signed-commits4/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.26user 2.53system 1:41.30elapsed 4%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (66184major+36384minor)pagefaults 0swaps
PASS: basica-o6a
RCS file:
/tmp/build-cvs-nightly-signed-commits4/cvs-sanity-signed-commits4/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-04-16 02:58:46 -0700; author: derekrprice; state: Exp; lines: +0
-0; commitid: kfzL9zu6QyZvhntr;
cvs [log aborted]: received abort signal
exit status was 1
FAIL: basica-o7
/bin/sh /home/users/d/de/derekrprice/cvs-nightly-signed-commits4/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.75user 3.19system 2:21.11elapsed 4%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (88615major+47194minor)pagefaults 0swaps
PASS: basica-o6a
RCS file:
/tmp/build-cvs-nightly-signed-commits4/cvs-sanity-signed-commits4/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-04-16 03:00:51 -0700; author: derekrprice; state: Exp; lines: +0
-0; commitid: TVOjJ7k2WBneintr;
cvs [log aborted]: received abort signal
exit status was 1
FAIL: basica-o7
- [Cvs-test-results] Nightly testing results for signed-commits4 (alpha Linux 2.2.20), cvstest, 2006/04/12
- [Cvs-test-results] Nightly testing results for signed-commits4 (alpha Linux 2.2.20), cvstest, 2006/04/13
- [Cvs-test-results] Nightly testing results for signed-commits4 (alpha Linux 2.2.20), cvstest, 2006/04/14
- [Cvs-test-results] Nightly testing results for signed-commits4 (alpha Linux 2.2.20), cvstest, 2006/04/15
- [Cvs-test-results] Nightly testing results for signed-commits4 (alpha Linux 2.2.20),
cvstest <=
- [Cvs-test-results] Nightly testing results for signed-commits4 (alpha Linux 2.2.20), cvstest, 2006/04/17
- [Cvs-test-results] Nightly testing results for signed-commits4 (alpha Linux 2.2.20), cvstest, 2006/04/18
- [Cvs-test-results] Nightly testing results for signed-commits4 (alpha Linux 2.2.20), cvstest, 2006/04/19
- [Cvs-test-results] Nightly testing results for signed-commits4 (alpha Linux 2.2.20), cvstest, 2006/04/20
- [Cvs-test-results] Nightly testing results for signed-commits4 (alpha Linux 2.2.20), cvstest, 2006/04/21