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 [EMAIL PROTECTED] 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. >
