db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3357) Reduce runtime of jdbcapi.DataSourceTest
Date Thu, 07 Feb 2008 18:11:09 GMT

     [ 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:
>            Reporter: Kristian Waagan
>            Priority: Trivial
>             Fix For:
>         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.

View raw message