[Developers] Unify screen layout of test suite results

Erik Schnetter schnetter at cct.lsu.edu
Tue Jan 30 13:54:42 CST 2007

On Jan 30, 2007, at 04:40:08, Tom Goodale wrote:

> On Tue, 30 Jan 2007, Thomas Radke wrote:
>> Erik Schnetter wrote:
>>> On Jan 26, 2007, at 09:48:57, Thomas Radke wrote:
>>>> Erik Schnetter wrote:
>>>>> I noticed that the test suite results are reported with an ad-hoc
>>>>> screen layout.  Some messages are preceded by an empty line,   
>>>>> others
>>>>> are
>>>>> not; some are indented 3 characters, others about 10 characters.
>>>>> I would like to use a uniform format: For each file about which  
>>>>> there
>>>>> is a message, indent by 3 spaces, if there is additional  
>>>>> information
>>>>> about that file, indent that by 6 spaces.  Each message begins   
>>>>> with
>>>>> the
>>>>> file name, followed by a colon.  Empty lines only between the
>>>>> different
>>>>> sections.
>>>>> Thomas, would that break your automated report parser?
>>>> Not where the reports for individual testsuites are concerned; this
>>>> information is stored in individual files "<testsuite>.diffs" in  
>>>> the
>>>> "TEST/<configuration>/<thorn>/" subdir and is simply imported as  
>>>> is  into
>>>> the integration test output.
>>>> The only information which is parsed by the integration test  
>>>> script is
>>>> the one stored in "TEST/<configuration>/summary.log" from which the
>>>> number of available testsuites and the number of passed/failed   
>>>> tests is
>>>> extracted.
>>>> So feel free to unify and beautify the testsuite script output  
>>>> as  you
>>>> like.
>>> Do we require a patch for this change?
>> I'd say this counts as documentation, it doesn't change any
>> functionality. Thus shouldn't need to go through our patch approval
>> procedure.
> Part of the reason for the patch procedure is to ensure that there is
> discussion beforehand and that people are in sync, so since this  
> has been
> discussed and isn't going to come as a surprise, and we've already  
> covered
> what might be broken by it, it should be fine to just go ahead.



Erik Schnetter <schnetter at cct.lsu.edu>

My email is as private as my paper mail.  I therefore support encrypting
and signing email messages.  Get my PGP key from www.keyserver.net.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://www.cactuscode.org/pipermail/developers/attachments/20070130/ad0b46d2/attachment-0001.bin 

More information about the Developers mailing list