[
https://issues.apache.org/jira/browse/DERBY-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569435#comment-13569435
]
Dag H. Wanvik commented on DERBY-4358:
--------------------------------------
> That method is only run on the endpoint of a trajectory.
Ah, thanks for enlightening me.
> The test was written to be run when vetting a release.
So, presumably, a candidate release does get to see this test before it goes
out, good :) Still, I guess it would be useful to be able to run it on trunk,
if nothing else to discover any issues earlier in the release process.
> Improvements to UpgradeTrajectoryTest
> -------------------------------------
>
> Key: DERBY-4358
> URL: https://issues.apache.org/jira/browse/DERBY-4358
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.6.1.0
> 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
