[jira] Updated: (DERBY-4154) DboPowersTest should not hard upgrade the system/wombat database
[ https://issues.apache.org/jira/browse/DERBY-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-4154: -- Affects Version/s: 10.4.2.1 10.3.3.1 backported to 10.4 and 10.3. Thanks Dag for the fix. > DboPowersTest should not hard upgrade the system/wombat database > > > Key: DERBY-4154 > URL: https://issues.apache.org/jira/browse/DERBY-4154 > Project: Derby > Issue Type: Bug > Components: Test >Affects Versions: 10.3.3.1, 10.4.2.0, 10.4.2.1, 10.5.1.1, 10.6.0.0 >Reporter: Kathey Marsden >Assignee: Dag H. Wanvik > Fix For: 10.5.1.2, 10.6.0.0 > > Attachments: derby-4154.diff, suitesAll-trunk-against-10_5-db.log > > > In order to test soft upgrade it is nice to be able to run tests against a > soft upgraded database. This currently cannot be done because DboPowersTest > hard upgrades system/wombat. It should do it's hard upgrade test against > another database. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-4154) DboPowersTest should not hard upgrade the system/wombat database
[ https://issues.apache.org/jira/browse/DERBY-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik updated DERBY-4154: - Attachment: suitesAll-trunk-against-10_5-db.log Attaching the output of a run of trunk with this patch of suites.All against a 10.5 "system/wombat". As far as I can see the errors and failures are to b expected, falling into two groups: - the new XPLAIN functionality - Schema name SYSIBM replaced with SYSCS_UTIL After the run I could still connect to system/wombat with the 10.5 Derby so it has not been hard upgraded in the run. > DboPowersTest should not hard upgrade the system/wombat database > > > Key: DERBY-4154 > URL: https://issues.apache.org/jira/browse/DERBY-4154 > Project: Derby > Issue Type: Bug > Components: Test >Affects Versions: 10.4.2.0, 10.5.1.1, 10.6.0.0 >Reporter: Kathey Marsden >Assignee: Dag H. Wanvik > Fix For: 10.6.0.0 > > Attachments: derby-4154.diff, suitesAll-trunk-against-10_5-db.log > > > In order to test soft upgrade it is nice to be able to run tests against a > soft upgraded database. This currently cannot be done because DboPowersTest > hard upgrades system/wombat. It should do it's hard upgrade test against > another database. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-4154) DboPowersTest should not hard upgrade the system/wombat database
[ https://issues.apache.org/jira/browse/DERBY-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik updated DERBY-4154: - Derby Info: [Patch Available] Fix Version/s: 10.6.0.0 > DboPowersTest should not hard upgrade the system/wombat database > > > Key: DERBY-4154 > URL: https://issues.apache.org/jira/browse/DERBY-4154 > Project: Derby > Issue Type: Bug > Components: Test >Affects Versions: 10.4.2.0, 10.5.1.1, 10.6.0.0 >Reporter: Kathey Marsden > Fix For: 10.6.0.0 > > Attachments: derby-4154.diff > > > In order to test soft upgrade it is nice to be able to run tests against a > soft upgraded database. This currently cannot be done because DboPowersTest > hard upgrades system/wombat. It should do it's hard upgrade test against > another database. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-4154) DboPowersTest should not hard upgrade the system/wombat database
[ https://issues.apache.org/jira/browse/DERBY-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik updated DERBY-4154: - Attachment: derby-4154.diff Uploading a patch for this, which makes the hard upgrade use another database, by wrapping the offending test cases in a singleUseDatabaseDecorator. I manually tested this by creating a system/wombat with a 10.4 release and then ran the test against trunk (with derby.database.allowPreReleaseUpgrade=true) and verified that after the run, I could still connect to system/wombat with a 10.4 Derby. Running full regressions now. Ready for review. > DboPowersTest should not hard upgrade the system/wombat database > > > Key: DERBY-4154 > URL: https://issues.apache.org/jira/browse/DERBY-4154 > Project: Derby > Issue Type: Bug > Components: Test >Affects Versions: 10.4.2.0, 10.5.1.1, 10.6.0.0 >Reporter: Kathey Marsden > Attachments: derby-4154.diff > > > In order to test soft upgrade it is nice to be able to run tests against a > soft upgraded database. This currently cannot be done because DboPowersTest > hard upgrades system/wombat. It should do it's hard upgrade test against > another database. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-4154) DboPowersTest should not hard upgrade the system/wombat database
[ https://issues.apache.org/jira/browse/DERBY-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-4154: -- Derby Categories: [Newcomer] > DboPowersTest should not hard upgrade the system/wombat database > > > Key: DERBY-4154 > URL: https://issues.apache.org/jira/browse/DERBY-4154 > Project: Derby > Issue Type: Bug > Components: Test >Affects Versions: 10.4.2.0, 10.5.1.1, 10.6.0.0 >Reporter: Kathey Marsden > > In order to test soft upgrade it is nice to be able to run tests against a > soft upgraded database. This currently cannot be done because DboPowersTest > hard upgrades system/wombat. It should do it's hard upgrade test against > another database. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
