Return-Path: 
 <jdo-dev-return-1099-apmail-db-jdo-dev-archive=www.apache.org@db.apache.org>
Delivered-To: apmail-db-jdo-dev-archive@www.apache.org
Received: (qmail 92911 invoked from network); 19 Aug 2005 09:38:31 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 19 Aug 2005 09:38:31 -0000
Received: (qmail 6971 invoked by uid 500); 19 Aug 2005 09:38:31 -0000
Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:jdo-dev-help@db.apache.org>
List-Unsubscribe: <mailto:jdo-dev-unsubscribe@db.apache.org>
List-Post: <mailto:jdo-dev@db.apache.org>
List-Id: <jdo-dev.db.apache.org>
Reply-To: jdo-dev@db.apache.org
Delivered-To: mailing list jdo-dev@db.apache.org
Received: (qmail 6955 invoked by uid 99); 19 Aug 2005 09:38:30 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Aug 2005 02:38:30 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Received: from [212.224.30.66] (HELO service-01.spree.de) (212.224.30.66)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Aug 2005 02:38:49 -0700
Received: from [172.16.1.19] (rio.spree.de [172.16.1.19])
	(authenticated bits=0)
	by service-01.spree.de (8.13.4/8.13.4/Debian-3) with ESMTP id j7J9cNSS017969
	for <jdo-dev@db.apache.org>; Fri, 19 Aug 2005 11:38:23 +0200
Message-ID: <4305A92E.1030801@spree.de>
Date: Fri, 19 Aug 2005 11:41:02 +0200
From: Michael Watzek <mwa.tech@spree.de>
Organization: Tech@Spree GmbH
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: jdo-dev@db.apache.org
Subject: Re: TCK logging proposal
References: <430206D6.9070102@spree.de>
 <54599.192.18.42.10.1124390697.squirrel@www.techatspree.com>
In-Reply-To: <54599.192.18.42.10.1124390697.squirrel@www.techatspree.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Hi Michael,

> Hi Michael,
> 
> I like the proposal. I added a few comments plus a suggestion for an
> extension below.
> 
> 
>>Hi,
>>
>>during last t-conference we discussed to improve logging of TCK runs.
>>Below, you find a summary of our discussion. Please comment!
>>
>>Current state:
>>Separate log files are written by JPOX, JPOX enhancer, Derby, and TCK.
>>The locations of these log files are:
>>
>>- JPOX: "target/jpox.log".
>>- JPOX enhancer: "target/enhanced/<identity type>/jpox.log"
>>- Derby: "target/database/derby/derby.log
>>- TCK: "target/logs/<timestamp>-<database>-<identity
>>type>-<configuration>.txt"
>>
>>The current logging configuration determines that JPOX and JPOX enhancer
>>append output to log files. Derby truncates the log file for each TCK
>>configuration. In contrast, the TCK writes a new log file for each TCK
>>configuration result.
>>
>>Problem:
>>Each component writes to a different log directory. The directories are
>>not under a common root. This fact complicates the log analysis. On the
>>other hand, the TCK writes a separate log file for each configuration
>>result to directory "target/logs". Currently, there are 14 different
>>configurations. There will be approximately 22 when the inheritance
>>proposal is implemented. Thus, each TCK run will produce 22 new files in
>>directory "target/logs". Obviously, this  fact reduces facility of
>>inspection.
> 
> 
> I agree, this does not work anymore, too many log files in that directory.
> 
> 
>>Proposal:
>>The proposal is to have separate log directories for each TCK run. These
>>log directories are located under the common parent directory
>>"target/logs". The naming pattern for these directories are given by
>>timestamp format "yyyyMMdd-HHmmss". The directory contents are:
>>
>>- Separate log file for each TCK configuration result. The naming
>>pattern is: "<database>-<identity type>-<configuration>.txt".
>>- Separate JPOX log file for each TCK configuration. The naming pattern
>>is: "<database>-<identity type>-<configuration>-jpox.txt".
> 
> 
> Sounds good.
> 
> 
>>Thus, each TCK run will produce 44 files in separate log directories.
> 
> 
> Just for my understanding: a TCK run will create one directory e.g.
> target/logs/20050818-101723. This directory contains all the logs files
> from the tck run including the TCK run results and the JPOX log output.
> The JPOX enhancer logs and the database log file do not go into this
> directory, they have their own directory, correct?
Correct. See below.

> 
> How about adding a new file showing a summary of the tck result for the
> different configurations. It would include two lines per configuration:
> - The first line shows the database, identitytype and the name of the
> configuration.
> - The second line lists the test results as we have it today at the end of
> the tck output:
> Tests run: 396,  Failures: 17,  Errors: 25, Time: 281,124 seconds.
> 
> This makese it easier to compare the results of this tck run with a
> prvious run. What do you think?
This is a good idea! What about "TCK.results" to be used as a file name. 
Concerning the format of the two lines per configuration, I suggest to 
have the file name of a particular configuration result as the first 
line, e.g.:

derby-app-alltests.txt:
     Tests run: 396,  Failures: 17,  Errors: 25, Time: 281,124 seconds.

I think, we need a final TCK output written to the console at the end of 
a TCK run, e.g.:

"All configuration passed." or
"5 configurations failed. See file 
'target/logs/20050818-165457/TCK.results' for details."

Regards,
Michael
> 
> 
>>The proposal is to write the JPOX enhancer log to directory
>>"target/logs/enhancer". There, separate files will be written for each
>>identity type. Successive enhancer runs append the log to these files.
>>The file name pattern is "<identity type>-jpox.txt".
>>
>>The proposal is to write the database log to directory
>>"target/logs/database". There, a common file for all identity types and
>>configurations will be written. Each run will append the log to that
>>file. The file name pattern is "<database>.txt"
>>
>>The log level of all components is "INFO".
> 
> 
> Sounds good.
> 
> Regads Michael
> 
> 
>>Regards,
>>Michael
>>--
>>-------------------------------------------------------------------
>>Michael Watzek                  Tech@Spree Engineering GmbH
>>mailto:mwa.tech@spree.de        Buelowstr. 66
>>Tel.:  ++49/30/235 520 36       10783 Berlin - Germany
>>Fax.:  ++49/30/217 520 12       http://www.spree.de/
>>-------------------------------------------------------------------
>>
> 
> 
> 


-- 
-------------------------------------------------------------------
Michael Watzek                  Tech@Spree Engineering GmbH
mailto:mwa.tech@spree.de        Buelowstr. 66
Tel.:  ++49/30/235 520 36       10783 Berlin - Germany
Fax.:  ++49/30/217 520 12       http://www.spree.de/
-------------------------------------------------------------------