Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <4334A6D4.2080901@Sourcery.Org>
Date: Fri, 23 Sep 2005 18:07:32 -0700
From: Satheesh Bandaram <satheesh@Sourcery.Org>
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
MIME-Version: 1.0
To: Derby Development <derby-dev@db.apache.org>
Subject: Re: [jira] Updated: (DERBY-579) Query timeout set for one statement
 may affect other statements with the same SQL string
References: <1216783041.1127225428457.JavaMail.jira@ajax.apache.org>
 <4333FF25.5080908@sun.com>
In-Reply-To: <4333FF25.5080908@sun.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I am not exactly objecting  :-) , but it would be nice to add a test
case to show the problem the fix is attempting to fix. I suspect the
original issue is easy to introduce, but hard to catch.

While we are on this topic, I noticed SetQueryTimeoutTest test takes
around 30-40 minutes on my laptop. On one of our build machines, it
actually runs for longer than 2 hours when the test harness actually
kills the test. (causing the test to fail everytime) Though this is more
of our test machine problem (it is really sloooow), taking 30-40 minutes
for one functional test seems too long. Is there anyway the test can be
made to run faster?

Satheesh

Oyvind.Bakksjo@Sun.COM wrote:

> Oyvind Bakksjo (JIRA) wrote:
>
>>      [ http://issues.apache.org/jira/browse/DERBY-579?page=all ]
>>
>> Oyvind Bakksjo updated DERBY-579:
>> ---------------------------------
>>
>>     Attachment: DERBY-579.svn.diff
>
>
> If nobody objects by end of business today (any timezone), I will
> commit this patch.
>