You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Deepa Remesh (JIRA)" <de...@db.apache.org> on 2006/08/14 18:03:13 UTC
[jira] Created: (DERBY-1689) Remove Upgrade_10_1_10_2 test from
10.3 and add new upgrade tests for 10.3
Remove Upgrade_10_1_10_2 test from 10.3 and add new upgrade tests for 10.3
--------------------------------------------------------------------------
Key: DERBY-1689
URL: http://issues.apache.org/jira/browse/DERBY-1689
Project: Derby
Issue Type: Task
Components: Test
Affects Versions: 10.3.0.0
Reporter: Deepa Remesh
Priority: Minor
Fix For: 10.3.0.0
The current upgrade test Upgrade_10_1_10_2 tests upgrade from 10.1 to 10.2. This test should continue to run in 10.2 branch. It is failing in the new trunk (10.3) because the test internally checks the versions. To resolve this failure, we should remove this test from running in new trunk and then create new upgrade tests to test new upgrade scenarios:
* 10.1 to 10.3
* 10.2 to 10.3
Upgrade test uses the UpgradeTester class which contains the test for various upgrade scenarios. To test any old/new release upgrade combination, we can create a new test which uses this class and pass in the old and new versions to the class. Any new upgrade scenarios for new features can be added to UpgradeTester (e.g, test for 10.2 feature grant/revoke was added to UpgradeTester).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1689) Remove Upgrade_10_1_10_2 test from
10.3 and add new upgrade tests for 10.3
Posted by "Andrew McIntyre (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1689?page=comments#action_12449868 ]
Andrew McIntyre commented on DERBY-1689:
----------------------------------------
Added the 10.2.1.6 release jars to http://svn.apache.org/repos/asf/db/derby/jars/10.2.1.6/ with revision 475072.
> Remove Upgrade_10_1_10_2 test from 10.3 and add new upgrade tests for 10.3
> --------------------------------------------------------------------------
>
> Key: DERBY-1689
> URL: http://issues.apache.org/jira/browse/DERBY-1689
> Project: Derby
> Issue Type: Task
> Components: Test, Regression Test Failure
> Affects Versions: 10.3.0.0
> Reporter: Deepa Remesh
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: remove_10_2_upg_test.diff
>
>
> The current upgrade test Upgrade_10_1_10_2 tests upgrade from 10.1 to 10.2. This test should continue to run in 10.2 branch. It is failing in the new trunk (10.3) because the test internally checks the versions. To resolve this failure, we should remove this test from running in new trunk and then create new upgrade tests to test new upgrade scenarios:
> * 10.1 to 10.3
> * 10.2 to 10.3
> Upgrade test uses the UpgradeTester class which contains the test for various upgrade scenarios. To test any old/new release upgrade combination, we can create a new test which uses this class and pass in the old and new versions to the class. Any new upgrade scenarios for new features can be added to UpgradeTester (e.g, test for 10.2 feature grant/revoke was added to UpgradeTester).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1689) Remove Upgrade_10_1_10_2 test from
10.3 and add new upgrade tests for 10.3
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1689?page=comments#action_12428274 ]
Rick Hillegas commented on DERBY-1689:
--------------------------------------
Committed remove_10_2_upg_test.diff at subversion revision 431744.
> Remove Upgrade_10_1_10_2 test from 10.3 and add new upgrade tests for 10.3
> --------------------------------------------------------------------------
>
> Key: DERBY-1689
> URL: http://issues.apache.org/jira/browse/DERBY-1689
> Project: Derby
> Issue Type: Task
> Components: Test, Regression Test Failure
> Affects Versions: 10.3.0.0
> Reporter: Deepa Remesh
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: remove_10_2_upg_test.diff
>
>
> The current upgrade test Upgrade_10_1_10_2 tests upgrade from 10.1 to 10.2. This test should continue to run in 10.2 branch. It is failing in the new trunk (10.3) because the test internally checks the versions. To resolve this failure, we should remove this test from running in new trunk and then create new upgrade tests to test new upgrade scenarios:
> * 10.1 to 10.3
> * 10.2 to 10.3
> Upgrade test uses the UpgradeTester class which contains the test for various upgrade scenarios. To test any old/new release upgrade combination, we can create a new test which uses this class and pass in the old and new versions to the class. Any new upgrade scenarios for new features can be added to UpgradeTester (e.g, test for 10.2 feature grant/revoke was added to UpgradeTester).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-1689) Remove Upgrade_10_1_10_2 test from
10.3 and add new upgrade tests for 10.3
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel John Debrunner resolved DERBY-1689.
------------------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 10.3.0.0)
I believe that this should be handled by the conversion of the upgrade testing to JUnit described in DERBY-2217
> Remove Upgrade_10_1_10_2 test from 10.3 and add new upgrade tests for 10.3
> --------------------------------------------------------------------------
>
> Key: DERBY-1689
> URL: https://issues.apache.org/jira/browse/DERBY-1689
> Project: Derby
> Issue Type: Task
> Components: Regression Test Failure, Test
> Affects Versions: 10.3.0.0
> Reporter: Deepa Remesh
> Priority: Minor
> Attachments: remove_10_2_upg_test.diff
>
>
> The current upgrade test Upgrade_10_1_10_2 tests upgrade from 10.1 to 10.2. This test should continue to run in 10.2 branch. It is failing in the new trunk (10.3) because the test internally checks the versions. To resolve this failure, we should remove this test from running in new trunk and then create new upgrade tests to test new upgrade scenarios:
> * 10.1 to 10.3
> * 10.2 to 10.3
> Upgrade test uses the UpgradeTester class which contains the test for various upgrade scenarios. To test any old/new release upgrade combination, we can create a new test which uses this class and pass in the old and new versions to the class. Any new upgrade scenarios for new features can be added to UpgradeTester (e.g, test for 10.2 feature grant/revoke was added to UpgradeTester).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1689) Remove Upgrade_10_1_10_2 test from
10.3 and add new upgrade tests for 10.3
Posted by "Bryan Pendleton (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1689?page=comments#action_12442302 ]
Bryan Pendleton commented on DERBY-1689:
----------------------------------------
Deepa, does this issue need to be addressed prior to committing any new trunk changes which include update functionality? For instance, there is a patch to DERBY-630 ready for commit. Will committing that patch complicate this issue?
> Remove Upgrade_10_1_10_2 test from 10.3 and add new upgrade tests for 10.3
> --------------------------------------------------------------------------
>
> Key: DERBY-1689
> URL: http://issues.apache.org/jira/browse/DERBY-1689
> Project: Derby
> Issue Type: Task
> Components: Test, Regression Test Failure
> Affects Versions: 10.3.0.0
> Reporter: Deepa Remesh
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: remove_10_2_upg_test.diff
>
>
> The current upgrade test Upgrade_10_1_10_2 tests upgrade from 10.1 to 10.2. This test should continue to run in 10.2 branch. It is failing in the new trunk (10.3) because the test internally checks the versions. To resolve this failure, we should remove this test from running in new trunk and then create new upgrade tests to test new upgrade scenarios:
> * 10.1 to 10.3
> * 10.2 to 10.3
> Upgrade test uses the UpgradeTester class which contains the test for various upgrade scenarios. To test any old/new release upgrade combination, we can create a new test which uses this class and pass in the old and new versions to the class. Any new upgrade scenarios for new features can be added to UpgradeTester (e.g, test for 10.2 feature grant/revoke was added to UpgradeTester).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1689) Remove Upgrade_10_1_10_2 test from
10.3 and add new upgrade tests for 10.3
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1689?page=comments#action_12442394 ]
Deepa Remesh commented on DERBY-1689:
-------------------------------------
Thanks Bryan for bringing this up. I see Yip has already submitted a patch for DERBY-630 with upgrade test for 10.1 to 10.3. Thanks Yip. And as Yip mentioned, for testing upgrade from 10.2 to 10.3, we will need to check in the 10.2 jars.
As we now have the 10.2 release jars available, it would be good if we can get it into svn similar to what was done for 10.1 jars. Andrew had done this for 10.1 here: http://issues.apache.org/jira/browse/DERBY-1049
And then we can add the upgrade test for 10.2 to 10.3 which should resolve this issue.
> Remove Upgrade_10_1_10_2 test from 10.3 and add new upgrade tests for 10.3
> --------------------------------------------------------------------------
>
> Key: DERBY-1689
> URL: http://issues.apache.org/jira/browse/DERBY-1689
> Project: Derby
> Issue Type: Task
> Components: Test, Regression Test Failure
> Affects Versions: 10.3.0.0
> Reporter: Deepa Remesh
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: remove_10_2_upg_test.diff
>
>
> The current upgrade test Upgrade_10_1_10_2 tests upgrade from 10.1 to 10.2. This test should continue to run in 10.2 branch. It is failing in the new trunk (10.3) because the test internally checks the versions. To resolve this failure, we should remove this test from running in new trunk and then create new upgrade tests to test new upgrade scenarios:
> * 10.1 to 10.3
> * 10.2 to 10.3
> Upgrade test uses the UpgradeTester class which contains the test for various upgrade scenarios. To test any old/new release upgrade combination, we can create a new test which uses this class and pass in the old and new versions to the class. Any new upgrade scenarios for new features can be added to UpgradeTester (e.g, test for 10.2 feature grant/revoke was added to UpgradeTester).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-1689) Remove Upgrade_10_1_10_2 test from 10.3
and add new upgrade tests for 10.3
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dyre Tjeldvoll closed DERBY-1689.
---------------------------------
> Remove Upgrade_10_1_10_2 test from 10.3 and add new upgrade tests for 10.3
> --------------------------------------------------------------------------
>
> Key: DERBY-1689
> URL: https://issues.apache.org/jira/browse/DERBY-1689
> Project: Derby
> Issue Type: Task
> Components: Regression Test Failure, Test
> Affects Versions: 10.3.1.4
> Reporter: Deepa Remesh
> Priority: Minor
> Attachments: remove_10_2_upg_test.diff
>
>
> The current upgrade test Upgrade_10_1_10_2 tests upgrade from 10.1 to 10.2. This test should continue to run in 10.2 branch. It is failing in the new trunk (10.3) because the test internally checks the versions. To resolve this failure, we should remove this test from running in new trunk and then create new upgrade tests to test new upgrade scenarios:
> * 10.1 to 10.3
> * 10.2 to 10.3
> Upgrade test uses the UpgradeTester class which contains the test for various upgrade scenarios. To test any old/new release upgrade combination, we can create a new test which uses this class and pass in the old and new versions to the class. Any new upgrade scenarios for new features can be added to UpgradeTester (e.g, test for 10.2 feature grant/revoke was added to UpgradeTester).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-1689) Remove Upgrade_10_1_10_2 test from
10.3 and add new upgrade tests for 10.3
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1689?page=all ]
Deepa Remesh updated DERBY-1689:
--------------------------------
Attachment: remove_10_2_upg_test.diff
Attaching a patch 'remove_10_2_upg_test.diff' which removes the test Upgrade_10_1_10_2 from running in the trunk. Upgrade_10_1_10_2 is part of upgrade suite and the patch removes it from upgrade.runall file. I ran upgrade suite to verify. I would appreciate if someone can commit this change. This change should not be merged back to 10.2 branch.
I willl submit another patch to add new upgrade test for upgrade from 10.1 to 10.3. Once 10.2 is released, we can check in the jars into svn and then create upgrade test for 10.2 to 10.3.
> Remove Upgrade_10_1_10_2 test from 10.3 and add new upgrade tests for 10.3
> --------------------------------------------------------------------------
>
> Key: DERBY-1689
> URL: http://issues.apache.org/jira/browse/DERBY-1689
> Project: Derby
> Issue Type: Task
> Components: Test, Regression Test Failure
> Affects Versions: 10.3.0.0
> Reporter: Deepa Remesh
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: remove_10_2_upg_test.diff
>
>
> The current upgrade test Upgrade_10_1_10_2 tests upgrade from 10.1 to 10.2. This test should continue to run in 10.2 branch. It is failing in the new trunk (10.3) because the test internally checks the versions. To resolve this failure, we should remove this test from running in new trunk and then create new upgrade tests to test new upgrade scenarios:
> * 10.1 to 10.3
> * 10.2 to 10.3
> Upgrade test uses the UpgradeTester class which contains the test for various upgrade scenarios. To test any old/new release upgrade combination, we can create a new test which uses this class and pass in the old and new versions to the class. Any new upgrade scenarios for new features can be added to UpgradeTester (e.g, test for 10.2 feature grant/revoke was added to UpgradeTester).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1689) Remove Upgrade_10_1_10_2 test from
10.3 and add new upgrade tests for 10.3
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1689?page=all ]
Deepa Remesh updated DERBY-1689:
--------------------------------
Component/s: Regression Test Failure
> Remove Upgrade_10_1_10_2 test from 10.3 and add new upgrade tests for 10.3
> --------------------------------------------------------------------------
>
> Key: DERBY-1689
> URL: http://issues.apache.org/jira/browse/DERBY-1689
> Project: Derby
> Issue Type: Task
> Components: Test, Regression Test Failure
> Affects Versions: 10.3.0.0
> Reporter: Deepa Remesh
> Priority: Minor
> Fix For: 10.3.0.0
>
>
> The current upgrade test Upgrade_10_1_10_2 tests upgrade from 10.1 to 10.2. This test should continue to run in 10.2 branch. It is failing in the new trunk (10.3) because the test internally checks the versions. To resolve this failure, we should remove this test from running in new trunk and then create new upgrade tests to test new upgrade scenarios:
> * 10.1 to 10.3
> * 10.2 to 10.3
> Upgrade test uses the UpgradeTester class which contains the test for various upgrade scenarios. To test any old/new release upgrade combination, we can create a new test which uses this class and pass in the old and new versions to the class. Any new upgrade scenarios for new features can be added to UpgradeTester (e.g, test for 10.2 feature grant/revoke was added to UpgradeTester).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira