db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-4358) Improvements to UpgradeTrajectoryTest
Date Thu, 31 Jan 2013 13:37:12 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567624#comment-13567624

Rick Hillegas commented on DERBY-4358:

Hi Dag,

Most of the actual assertions in the test occur inside compareDatabases(). That method is
only run on the endpoint of a trajectory. If we ran compareDatabases() on the interior points,
then we could eliminate trajectories which were continued by other trajectories. We would
need to convince ourselves that compareDatabases() does not alter the database.

The test was written to be run when vetting a release. So it was only concerned with production
builds and not with alpha builds like the trunk. We could add the trunk as an endpoint. That
might involve wrapping the test in a property setter in order to set the special flag which
allows upgrade to alpha builds.
> Improvements to UpgradeTrajectoryTest
> -------------------------------------
>                 Key: DERBY-4358
>                 URL: https://issues.apache.org/jira/browse/DERBY-4358
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions:
>            Reporter: Ole Solberg
> A task to contain the improvements we see needed for the UpgradeTrajectoryTest.
> I have so far seen problems running the test on JVM 1.6,
> and when running on JVM 1.5 seen memory exhaustion and extreme execution time for upgrades.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message