[DERBY-4358] Improvements to UpgradeTrajectoryTest

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.6.1.0
• Component/s: Test
• Assignee: Unassigned
• Reporter: Ole Solberg
• Created: 25/Aug/09 13:07
• Updated: 02/Feb/13 15:20

Description

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.

Issue Links

• is related to: DERBY-4157 Create a test to verify that virgin metadata is identical to hard-upgraded metadata

Sub-Tasks

• Avoid memory exhaustion when running UpgradeTrajectoryTest w/-DderbyTesting.allTrajectories=true: Open