[
https://issues.apache.org/jira/browse/DERBY-5486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143890#comment-13143890
]
Knut Anders Hatlen commented on DERBY-5486:
-------------------------------------------
Are we confident that the intermittent failures are problems with the tests and
not with the implementation? If so, just removing the tests sounds OK. But if
there's potentially a problem with the implementation, that problem will still
be there after the removal of the tests...
> Upgrade tests should verify that DERBY-4437 was backed out of 10.8.2.2
> ----------------------------------------------------------------------
>
> Key: DERBY-5486
> URL: https://issues.apache.org/jira/browse/DERBY-5486
> Project: Derby
> Issue Type: Improvement
> Components: SQL, Test
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-5486-01-ab-mergeFiles.diff,
> derby-5486-02-aa-removeTests.diff
>
>
> The following code in UpgradeRun needs to be reworked to verify that
> sequence/identities behave as expected when upgrading from 10.8.2.2:
> if ( lessThan( version, new int[] { 10, 8, 1, 6 } ) )
> { suite.addTest(Changes10_8_2.suite(phase)); }
> The following might do the trick:
> if (oldMinor < 7)
> suite.addTest(Changes10_7.suite(phase));
> if (oldMinor < 9)
> {
> suite.addTest(Changes10_9.suite(phase));
> suite.addTest(Changes10_8_2.suite(phase));
> }
> Thanks to Kristian for spotting this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
