Return-Path: 
 <user-return-50948-apmail-ant-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-user-archive@www.apache.org
Received: (qmail 52961 invoked from network); 1 Jul 2005 20:01:14 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 1 Jul 2005 20:01:14 -0000
Received: (qmail 94338 invoked by uid 500); 1 Jul 2005 20:01:07 -0000
Delivered-To: apmail-ant-user-archive@ant.apache.org
Received: (qmail 94308 invoked by uid 500); 1 Jul 2005 20:01:06 -0000
Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:user-unsubscribe@ant.apache.org>
List-Help: <mailto:user-help@ant.apache.org>
List-Post: <mailto:user@ant.apache.org>
List-Id: "Ant Users List" <user.ant.apache.org>
Reply-To: "Ant Users List" <user@ant.apache.org>
Delivered-To: mailing list user@ant.apache.org
Received: (qmail 94295 invoked by uid 99); 1 Jul 2005 20:01:06 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jul 2005 13:01:06 -0700
X-ASF-Spam-Status: No, hits=0.1 required=10.0
	tests=FORGED_RCVD_HELO
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of bmf@opentext.com designates
 204.138.115.203 as permitted sender)
Received: from [204.138.115.203] (HELO opentext.com) (204.138.115.203)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jul 2005 13:01:08 -0700
Received: from otwlpm01.smtp.dmz.opentext.com (otwlpm01.smtp.dmz.opentext.com
 [192.168.15.230])
	by opentext.com (8.12.8/8.12.8) with ESMTP id j61K12Fc018031
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <user@ant.apache.org>; Fri, 1 Jul 2005 16:01:03 -0400
Received: from vectorsvc.wl.opentext.com (ava.wl.opentext.com [172.21.5.96])
	by otwlpm01.smtp.dmz.opentext.com (8.13.1/8.13.1) with ESMTP id
 j61K12BT010381
	for <user@ant.apache.org>; Fri, 1 Jul 2005 16:01:02 -0400
Received: from OTWATMX01.opentext.net (kelly.wl.opentext.com [192.168.15.10])
	by vectorsvc.wl.opentext.com (8.12.8/8.12.8) with ESMTP id j61K12sn018020
	for <user@ant.apache.org>; Fri, 1 Jul 2005 16:01:02 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: junit timeout bug
Date: Fri, 1 Jul 2005 16:01:00 -0400
Message-ID: <5413CE32D1459C46A39F053C6A2636AE038CDD66@OTWATMX01.opentext.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: junit timeout bug
Thread-Index: AcV+d5oUBPrfGGoAQgmTcq5fpgkREg==
From: "Brian Fitzpatrick" <bmf@opentext.com>
To: <user@ant.apache.org>
X-Archived: msg.1nDjAGa:2005-07-01:otwlpm01.smtp.dmz.opentext.com
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

When a <junit> timeout occurs, the formatter log files do not contain
the logs of the test, though if you use "showoutput=3Dtrue" the logs are
visible on the console. This seems to be a bug to me, but I wanted to
confirm it before reporting it.

If I have a formatter set up for the <junit> task and a timeout occurs
during a test execution, then the log output of the test does not appear
in the formatter text file.  However, if I specify "showoutput=3Dtrue" =
in
the <junit> task, then the output of the test appears in the console.

<junit
	printsummary=3D"true"
	fork=3D"true"
	dir=3D"${ecm.basedir}"
	haltonfailure=3D"true"
	failureproperty=3D"test.failed"
	timeout=3D"600000"
	maxmemory=3D"1024m"
	showoutput=3D"${junit.showoutput}">

	<formatter type=3D"brief" />
	<formatter type=3D"xml" />

If a timeout occurs after 10 minutes, the *.TXT and *.XML files of the
formatter do not contain any log output. They only have a couple of
lines indicating that a timeout occurred.

However, if I set showoutput to true, then the console contains all of
the logging data of the test prior to the timeout, which makes it much
easier to figure out why the test timed out.

In our case, we use the MailLogger to send out the log, so we can't have
all the output going to the console, since it grows too large to be sent
via e-mail.

The doc for the showoutput attribute indicates that it should be the
same data that goes to the formatters:

Showoutput - Send any output generated by tests to Ant's logging system
as well as to the formatters. By default only the formatters receive the
output.

=20

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org