[
https://issues.apache.org/jira/browse/DERBY-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567517#comment-13567517
]
Dag H. Wanvik commented on DERBY-4358:
--------------------------------------
It seems allTrajecotries=trye doesn't prune redundant combinations, e.g. I saw
this when running all combinations above 10.6.2.1 (with
-Dderby.tests.debug=true):
DEBUG: Testing trajectory: 10.6.2.1 -> 10.7.1.1 -> 10.8.1.2 -> 10.8.2.2 ->
10.8.3.0 -> 10.9.1.0 ( hard, hard, hard, hard, hard, hard )
.DEBUG: Testing trajectory: 10.6.2.1 -> 10.7.1.1 -> 10.8.1.2 -> 10.8.2.2 ->
10.8.3.0 ( hard, hard, hard, hard, hard )
The second is a pure subset of the first and doesn't add value as far as I can
see. Btw, does this test ever use the current trunk as an upgrade target (i.e.
using derby.database.allowPreReleaseUpgrade=true)? If not, why not?
> 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
