Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 59111 invoked from network); 7 Feb 2008 18:11:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Feb 2008 18:11:30 -0000 Received: (qmail 84187 invoked by uid 500); 7 Feb 2008 18:11:22 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 84156 invoked by uid 500); 7 Feb 2008 18:11: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 84147 invoked by uid 99); 7 Feb 2008 18:11:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Feb 2008 10:11:22 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Feb 2008 18:11:01 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 5A34D714077 for ; Thu, 7 Feb 2008 10:11:09 -0800 (PST) Message-ID: <68235.1202407869366.JavaMail.jira@brutus> Date: Thu, 7 Feb 2008 10:11:09 -0800 (PST) From: "Myrna van Lunteren (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-3357) Reduce runtime of jdbcapi.DataSourceTest In-Reply-To: <15151149.1201596994112.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrna van Lunteren updated DERBY-3357: -------------------------------------- Attachment: DERBY-3357_otherspeedup.diff Because I did the original conversion, I felt honor-bound to try address Dan's comments... I'm attaching a patch that I think makes the suite() method more complicated, but does differentiate at that level between which tests should run with client, server, or both, and the creation of the tables is done in a CleanDatabaseTestSetup.decorateSQL method. The test only gained a few seconds on my machine. I'm not sure whether the added complexity of the client/server/both split is worth the few seconds at run time. Opinions? > Reduce runtime of jdbcapi.DataSourceTest > ---------------------------------------- > > Key: DERBY-3357 > URL: https://issues.apache.org/jira/browse/DERBY-3357 > Project: Derby > Issue Type: Improvement > Components: Test > Affects Versions: 10.4.0.0 > Reporter: Kristian Waagan > Priority: Trivial > Fix For: 10.4.0.0 > > Attachments: derby-3357-1a-lower_lock_timeout.diff, DERBY-3357_otherspeedup.diff > > > Two tests in DataSoureTest are waiting for a lock timeout. The runtime of the suite could be reduced by setting the lock timeout to a lower value. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.