Return-Path: 
 <derby-dev-return-25673-apmail-db-derby-dev-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-derby-dev-archive@www.apache.org
Received: (qmail 55522 invoked from network); 2 Aug 2006 15:50:48 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 2 Aug 2006 15:50:48 -0000
Received: (qmail 68520 invoked by uid 500); 2 Aug 2006 15:50:46 -0000
Delivered-To: apmail-db-derby-dev-archive@db.apache.org
Received: (qmail 68490 invoked by uid 500); 2 Aug 2006 15:50:46 -0000
Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:derby-dev-help@db.apache.org>
List-Unsubscribe: <mailto:derby-dev-unsubscribe@db.apache.org>
List-Post: <mailto:derby-dev@db.apache.org>
List-Id: <derby-dev.db.apache.org>
Reply-To: <derby-dev@db.apache.org>
Delivered-To: mailing list derby-dev@db.apache.org
Received: (qmail 68481 invoked by uid 99); 2 Aug 2006 15:50:46 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Aug 2006 08:50:46 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=UNPARSEABLE_RELAY
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Received: from [192.18.42.249] (HELO nwkea-pix-1.sun.com) (192.18.42.249)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Aug 2006 08:50:44 -0700
Received: from d1-sfbay-10.sun.com ([192.18.39.120])
	by nwkea-pix-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id k72FoO2b005269
	for <derby-dev@db.apache.org>; Wed, 2 Aug 2006 08:50:24 -0700 (PDT)
Received: from conversion-daemon.d1-sfbay-10.sun.com by d1-sfbay-10.sun.com
 (Sun Java System Messaging Server 6.2-4.02 (built Sep  9 2005))
 id <0J3D00401NZEMB00@d1-sfbay-10.sun.com>
 (original mail from Richard.Hillegas@Sun.COM) for derby-dev@db.apache.org;
 Wed, 02 Aug 2006 08:50:24 -0700 (PDT)
Received: from [129.150.20.94] by d1-sfbay-10.sun.com
 (Sun Java System Messaging Server 6.2-4.02 (built Sep  9 2005))
 with ESMTPSA id <0J3D00F1KNZZ4490@d1-sfbay-10.sun.com> for
 derby-dev@db.apache.org; Wed, 02 Aug 2006 08:50:24 -0700 (PDT)
Date: Wed, 02 Aug 2006 08:50:33 -0700
From: Rick Hillegas <Richard.Hillegas@Sun.COM>
Subject: Re: is it expected that there is no "time" bomb for junit tests?
In-reply-to: <44D0C140.7000503@sbcglobal.net>
Sender: Richard.Hillegas@Sun.COM
To: derby-dev@db.apache.org
Message-id: <44D0C9C9.7060405@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
References: <44D0C140.7000503@sbcglobal.net>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

The following link explains how to set the timeout for an individual 
JUnit test case--however, this mechanism requires jdk1.5 or higher:

http://www.instrumentalservices.com/content/view/45/52/#_Timing_out_a_test

In addition, if you run JUnit tests under ant, you can use the timeout 
attribute of the <junit> task. Do we  have a timeout mechanism for the 
current, home-grown test harness?

Mike Matrigali wrote:

> While running derbyall my run hung all night on a junit test,
> I assume this is expected if the test hung.
>