Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 30859 invoked from network); 6 Dec 2007 01:27:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Dec 2007 01:27:34 -0000 Received: (qmail 54039 invoked by uid 500); 6 Dec 2007 01:27:22 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 53999 invoked by uid 500); 6 Dec 2007 01:27:22 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 53989 invoked by uid 99); 6 Dec 2007 01:27:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Dec 2007 17:27:22 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [68.142.198.211] (HELO smtp112.sbc.mail.mud.yahoo.com) (68.142.198.211) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 06 Dec 2007 01:27:01 +0000 Received: (qmail 51354 invoked from network); 6 Dec 2007 01:27:02 -0000 Received: from unknown (HELO ?192.168.254.144?) (ddebrunner@sbcglobal.net@75.24.104.186 with plain) by smtp112.sbc.mail.mud.yahoo.com with SMTP; 6 Dec 2007 01:27:02 -0000 X-YMail-OSG: xZVhtH8VM1luibDrVxGq1VuokfTPkBvoj1ct0vAEd2Qhy5ryibn_igaPlMgkeCdNuZdizimJbg-- Message-ID: <47574FE7.4080608@apache.org> Date: Wed, 05 Dec 2007 17:27:03 -0800 From: Daniel John Debrunner User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: ok to add optional timeout/sleep property for junit framework? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Myrna van Lunteren wrote: > Hi, > > The junit networkserver tests run with a setting that's specified in - > at least - NetworkServerTestSetup. > I find that this may not be applicable for all machines; I ran on some > slower machines and the setting wasn't enough. > > I remember that one of the detractors for the old test harness was > that it had so many properties one could set, but I'm wondering if it > would be ok to add an optional system property for this. > Currently, I have a choice to either cook up derbyTesting.jar, or make > the changes for my slow machine applicable to everyone, and I'd rather > have an optional overwrite. > > Thoughts? Could this really be a bug, if the server doesn't start in over five minutes, even on a slow machine? Dan.