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 "Myrna van Lunteren (JIRA)" <de...@db.apache.org> on 2006/08/22 20:06:13 UTC
[jira] Created: (DERBY-1746) upgrade tests should start using
10.1.3 released builds
upgrade tests should start using 10.1.3 released builds
-------------------------------------------------------
Key: DERBY-1746
URL: http://issues.apache.org/jira/browse/DERBY-1746
Project: Derby
Issue Type: Test
Components: Test
Affects Versions: 10.2.1.0
Reporter: Myrna van Lunteren
Priority: Minor
Fix For: 10.2.1.0
The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
703d702
< ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
2168d2166
< ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
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
Re: [jira] Commented: (DERBY-1746) upgrade tests should start using 10.1.3 released builds
Posted by Deepa Remesh <dr...@gmail.com>.
On 8/24/06, Rick Hillegas (JIRA) <de...@db.apache.org> wrote:
> In addition, I don't think we should be running a test called 10_1_10_2 in the trunk. We should be running some other tests, perhaps 10_1_to_Current and 10_2_to_Current in the trunk. Perhaps 10_1_10_2 becomes the basis for 10_1_to_Current.
Upgrade_10_1_10_2 has been removed from running as part of derbyall in
the trunk. DERBY-1689 is open for adding new upgrade tests for trunk.
Instead of adding a new test for testing upgrade from 10.1, I now
think it is better to rename Upgrade_10_1_10_2 to Upgrade_From_10_1.
This way, we can use the same test in 10.2 and trunk. In the test's
version in trunk, we will need to change the "new version" to 10.3.
Later once 10.2 jars are released, we can similarly create a new test
Upgrade_From_10_2 and make it part of trunk. This test can then be
used in all later 10.x versions.
If this sounds okay, I'll submit patch to rename the current upgrade
test and attach it to DERBY-1689.
Thanks,
Deepa
[jira] Commented: (DERBY-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Myrna van Lunteren (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1746?page=comments#action_12430753 ]
Myrna van Lunteren commented on DERBY-1746:
-------------------------------------------
I was under the impression the upgrade test would only work with jars, and when one builds jars & runs with those after changing the externals that sealing violation error does not occur.
Further research is needed; patch was not ready for commit.
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: http://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.1.0
>
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
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-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren resolved DERBY-1746.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.3.0.0
In a discussion on the list, Dan suggested the test could automatically access the old version's jars from https://svn.apache.org/repos/asf/db/derby/jars.
Implemented this - and committed with revision 538724.
To repeat what I said on the list I'd do:
- I left the checked in derby*.jar files in https://svn.apache.org/repos/asf/db/derby/jars as is.
- I removed the 'lib' subdirectory from the upgrade tests' needs.
- I removed the svn:externals property from java/tools/testing.
The way it will work now, is:
- if the derbyTesting.oldReleasePath property is not set, the test
will attempt to access the jars from
https://svn.apache.org/repos/asf/db/derby/jars. If svn.apache.org is
not accessible (either because there is no network, or there is some
other problem with connecting to svn.apache.org), the tests will run
but fail.
- if the property is set, the test will attempt to access the jars
directly underneath
subdirectories with the version strings. If the jars are not found,
the tests will get skipped.
So, after my change the following command:
> java -DderbyTesting.oldReleasePath=/home/myrna/oldderbyreleases
junit.textui.TestRunner
org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite
will look for the following files:
/home/myrna/oldderbyreleases/10.0.2.1/derby.jar
/home/myrna/oldderbyreleases/10.1.1.0/derby.jar
/home/myrna/oldderbyreleases/10.1.2.1/derby.jar
/home/myrna/oldderbyreleases/10.1.3.1/derby.jar
/home/myrna/oldderbyreleases/10.2.1.6/derby.jar
/home/myrna/oldderbyreleases/10.2.2.0/derby.jar
This also means, that if you have been running with the property set
and dirs with the 'lib' in the path (for example:
/home/myrna/oldderbyreleases/10.0.2.1/lib/derby.jar) you will now not
get any tests run for that old release.
The only way upgrade tests will not run with suites.All is if the
property has been set to an incorrect/non-existing directory.
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: https://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff, svn_external
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (DERBY-1746) upgrade tests should start using 10.1.3 released builds
Posted by Myrna van Lunteren <m....@gmail.com>.
On 8/28/06, Kristian Waagan <Kr...@sun.com> wrote:
> Myrna van Lunteren (JIRA) wrote:
> > [ http://issues.apache.org/jira/browse/DERBY-1746?page=comments#action_12431034 ]
> >
> > Myrna van Lunteren commented on DERBY-1746:
> > -------------------------------------------
> >
> > I experimented and found the following:
> > - the problem appears to be with 10.1.3.1 derby.jar. Using the other 10.1.3.1 jars don't cause the same trouble.
> > - comparing the 10.1.1.0 derby.jar and 10.1.3.1 derby.jar it seemed the main difference was that the 10.1.3.1. does not have the directories in the jar.
> > - When I unjarred 10.1.3.1 derby.jar with jar -tvf, and then jar-ed back up using jar -xvf *, the resulting derby.jar could be used & the test did not give the sealing error.
>
> Hi Myrna,
>
> This is just a shot in the dark, I have not investigated on my own.
> You say that you unjarred 10.1.3.1, then jar-ed the files back up. By
> looking at the jar command used, a manifest does not seem to be specified.
> Could the reason why the re-packaged jar is working be because it simply
> isn't sealed, as I suppose the official 10.1.3.1 jars are?
>
>
> --
> Kristian
>
I thought about that, but I assumed that if I unjarred a jar file that
has a manifest (as the original 10.1.3.1 derby.jar has) this manifest
also got unjarred, and thus, when jarring it back up, the manifest
would get jarred back up also...
Naive, probably...But the jar does contain the a manifest again.
I'll see if poking at that gives me some clues.
Myrna
Re: [jira] Commented: (DERBY-1746) upgrade tests should start using
10.1.3 released builds
Posted by Kristian Waagan <Kr...@Sun.COM>.
Myrna van Lunteren (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-1746?page=comments#action_12431034 ]
>
> Myrna van Lunteren commented on DERBY-1746:
> -------------------------------------------
>
> I experimented and found the following:
> - the problem appears to be with 10.1.3.1 derby.jar. Using the other 10.1.3.1 jars don't cause the same trouble.
> - comparing the 10.1.1.0 derby.jar and 10.1.3.1 derby.jar it seemed the main difference was that the 10.1.3.1. does not have the directories in the jar.
> - When I unjarred 10.1.3.1 derby.jar with jar -tvf, and then jar-ed back up using jar -xvf *, the resulting derby.jar could be used & the test did not give the sealing error.
Hi Myrna,
This is just a shot in the dark, I have not investigated on my own.
You say that you unjarred 10.1.3.1, then jar-ed the files back up. By
looking at the jar command used, a manifest does not seem to be specified.
Could the reason why the re-packaged jar is working be because it simply
isn't sealed, as I suppose the official 10.1.3.1 jars are?
--
Kristian
>
> This is very strange, does this mean the 10.1.3.1 jars are bad?
> I welcome any suggestions on how to proceed.
>
>
>> upgrade tests should start using 10.1.3 released builds
>> -------------------------------------------------------
>>
>> Key: DERBY-1746
>> URL: http://issues.apache.org/jira/browse/DERBY-1746
>> Project: Derby
>> Issue Type: Test
>> Components: Test
>> Affects Versions: 10.2.1.0
>> Reporter: Myrna van Lunteren
>> Assigned To: Myrna van Lunteren
>> Priority: Minor
>> Fix For: 10.2.1.0
>>
>> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>>
>>
>> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
>> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
>> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
>> 703d702
>> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
>> 2168d2166
>> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
>> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
>
[jira] Commented: (DERBY-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Myrna van Lunteren (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1746?page=comments#action_12431034 ]
Myrna van Lunteren commented on DERBY-1746:
-------------------------------------------
I experimented and found the following:
- the problem appears to be with 10.1.3.1 derby.jar. Using the other 10.1.3.1 jars don't cause the same trouble.
- comparing the 10.1.1.0 derby.jar and 10.1.3.1 derby.jar it seemed the main difference was that the 10.1.3.1. does not have the directories in the jar.
- When I unjarred 10.1.3.1 derby.jar with jar -tvf, and then jar-ed back up using jar -xvf *, the resulting derby.jar could be used & the test did not give the sealing error.
This is very strange, does this mean the 10.1.3.1 jars are bad?
I welcome any suggestions on how to proceed.
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: http://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.1.0
>
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
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-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1746?page=all ]
Rick Hillegas updated DERBY-1746:
---------------------------------
Fix Version/s: 10.2.2.0
(was: 10.2.1.0)
Moving to 10.2.2.0.
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: http://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.2.0
>
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
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-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Myrna van Lunteren (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1746?page=comments#action_12431037 ]
Myrna van Lunteren commented on DERBY-1746:
-------------------------------------------
For the record, this is the 'full' stack trace from the .tmp file (no derby.log appears to get created)
START - phase CREATE
java.lang.ExceptionInInitializerError
at org.apache.derby.jdbc.EmbeddedDataSource.findDriver(Unknown Source)
at org.apache.derby.jdbc.EmbeddedDataSource.getConnection(Unknown Source)
at org.apache.derby.jdbc.EmbeddedDataSource.getConnection(Unknown Source)
at org.apache.derbyTesting.functionTests.tests.upgradeTests.UpgradeTester.getConnectionUsingDataSource(UpgradeTester.java:461)
at org.apache.derbyTesting.functionTests.tests.upgradeTests.UpgradeTester.getConnection(UpgradeTester.java:418)
at org.apache.derbyTesting.functionTests.tests.upgradeTests.UpgradeTester.runPhase(UpgradeTester.java:357)
at org.apache.derbyTesting.functionTests.tests.upgradeTests.UpgradeTester.runUpgradeTests(UpgradeTester.java:317)
at org.apache.derbyTesting.functionTests.tests.upgradeTests.Upgrade_10_1_10_2.main(Upgrade_10_1_10_2.java:44)
Caused by: java.lang.SecurityException: sealing violation: can't seal package org.apache.derby.iapi.services.crypto: already loaded
at java.net.URLClassLoader.defineClass(URLClassLoader.java:234)
at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at org.apache.derby.impl.services.monitor.BaseMonitor.getImplementations(Unknown Source)
at org.apache.derby.impl.services.monitor.BaseMonitor.getDefaultImplementations(Unknown Source)
at org.apache.derby.impl.services.monitor.BaseMonitor.runWithState(Unknown Source)
at org.apache.derby.impl.services.monitor.FileMonitor.<init>(Unknown Source)
at org.apache.derby.iapi.services.monitor.Monitor.startMonitor(Unknown Source)
at org.apache.derby.iapi.jdbc.JDBCBoot.boot(Unknown Source)
at org.apache.derby.jdbc.EmbeddedDriver.boot(Unknown Source)
at org.apache.derby.jdbc.EmbeddedDriver.<clinit>(Unknown Source)
... 8 more
Exception in thread "main"
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: http://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.1.0
>
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
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
Re: [jira] Commented: (DERBY-1746) upgrade tests should start using
10.1.3 released builds
Posted by Mike Matrigali <mi...@sbcglobal.net>.
I recently set up my environment for the upgrade tests, and believe that
it would be nice if the format stored in SVN matched the format that the
upgrade tests expect. It wasn't hard, I just had a script that copied
the svn dest jars to a place with the extra lib level - but it did seem
like another step that could go wrong for someone setting this up for
themselves.
I do agree it would be nice to get agreement for those maintaining
nightly runs that they would like to see the change and will respond to
get their env working.
Myrna van Lunteren (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/DERBY-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495813 ]
>
> Myrna van Lunteren commented on DERBY-1746:
> -------------------------------------------
>
> I'm confused. What is 'the existing format' and which are the 'changes discussed' ?
>
> I think it would be no great hardship to change scripts for running nightly tests, but I'm missing some info in this bug...Should I be looking at another bu that has the info you mention? Or is there a log of the IRC chat?
>
>
>>upgrade tests should start using 10.1.3 released builds
>>-------------------------------------------------------
>>
>> Key: DERBY-1746
>> URL: https://issues.apache.org/jira/browse/DERBY-1746
>> Project: Derby
>> Issue Type: Test
>> Components: Test
>> Affects Versions: 10.2.1.6
>> Reporter: Myrna van Lunteren
>> Priority: Minor
>> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff, svn_external
>>
>>
>>The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
>>However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
>>If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
>>703d702
>>< ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
>>2168d2166
>>< ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
>>It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
>
>
[jira] Commented: (DERBY-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495813 ]
Myrna van Lunteren commented on DERBY-1746:
-------------------------------------------
I'm confused. What is 'the existing format' and which are the 'changes discussed' ?
I think it would be no great hardship to change scripts for running nightly tests, but I'm missing some info in this bug...Should I be looking at another bu that has the info you mention? Or is there a log of the IRC chat?
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: https://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Myrna van Lunteren
> Priority: Minor
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff, svn_external
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Myrna van Lunteren (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1746?page=all ]
Myrna van Lunteren updated DERBY-1746:
--------------------------------------
Derby Info: [Patch Available]
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: http://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.1.0
>
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
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-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Myrna van Lunteren (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1746?page=all ]
Myrna van Lunteren updated DERBY-1746:
--------------------------------------
Attachment: DERBY-1746_102_20060823.stat
DERBY-1746_102_20060823.diff
DERBY-1746_trunk_20060824.diff
Attaching patches for this - DERBY-1746_102_20060823.diff modifies the master & updates the snv:externals property for the directory <10.2>/tools/testing/derby, and DERBy-1746_trunk_20060823.diff does the same for the trunk.
The trunk patch is a bit odd because I made a manual change - when I run the test right now it fails because of failing version compare tests. I think these diffs are to be expected currently, but I did not want to check that in as a master, I think that needs to be looked at separately...It seems as the trunk is no longer 10.2 this test needs to get changed/renamed, and I didn't want to address that here.
I assume patch or eclipse-apply-patch won't deal with the changing of properties, so here is the svn command:
(when cd-ed to the top of the branch)
cd tools/testing
svn propedit svn:externals derby
& change to:
derby/10.1 https://svn.apache.org/repos/asf/db/derby/jars/10.1.3.1
(note: svn update required after to see the files changed)
Thx to andrew for adding the 10.1.3.1 jars already.
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: http://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.1.0
>
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
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-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1746?page=all ]
Myrna van Lunteren updated DERBY-1746:
--------------------------------------
Affects Version/s: 10.2.3.0
(was: 10.2.1.6)
I've not had any ideas to fix the problem with the 10.1.3. jars.
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: http://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.3.0
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.2.0
>
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
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] Assigned: (DERBY-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Myrna van Lunteren (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1746?page=all ]
Myrna van Lunteren reassigned DERBY-1746:
-----------------------------------------
Assignee: Myrna van Lunteren
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: http://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.1.0
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
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-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462416 ]
Daniel John Debrunner commented on DERBY-1746:
----------------------------------------------
I'm working on an approach for this where the testing classes are always loaded from the "new" class loader and only the database code is loaded from the old loader. However it's much cleaner to do this in the pure junit world so I'm also experimenting with converting the upgrade tests to Junit.
The change involves making the code that loads the data source use the thread context loader instead of just Class.forName.
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: https://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.3.0
>
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
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] Updated: (DERBY-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1746?page=all ]
Myrna van Lunteren updated DERBY-1746:
--------------------------------------
Fix Version/s: 10.2.3.0
(was: 10.2.2.0)
Affects Version/s: 10.2.1.6
(was: 10.2.3.0)
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: http://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.3.0
>
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
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-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Mamta A. Satoor (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1746?page=comments#action_12430195 ]
Mamta A. Satoor commented on DERBY-1746:
----------------------------------------
The patch DERBY-1746_trunk_20060824.diff looks good to me for commit.
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: http://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.1.0
>
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
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-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Myrna van Lunteren (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1746?page=all ]
Myrna van Lunteren updated DERBY-1746:
--------------------------------------
Derby Info: (was: [Patch Available])
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: http://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.1.0
>
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
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-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-1746:
----------------------------------
Attachment: svn_external
Andrew and I had a chat on IRC about this. I was going to make the changes discussed but it looked like both Sun and IBM nightlies started using the existing format, so I dropped it.
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: https://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Myrna van Lunteren
> Priority: Minor
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff, svn_external
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Andrew McIntyre (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462385 ]
Andrew McIntyre commented on DERBY-1746:
----------------------------------------
I took a look at this issue and I've come to an impasse. The sealing problem that Myrna encountered is due to the fact that the 10.1.3.1 jars, unlike the 10.1.1.0 jars, are sealed. When running from the classes directory, UpgradeTester puts the entire classes directory into the ClassLoader because it needs some of the testing classes from the newer version. Unfortunately, this also puts all of the newer Derby classes into the classloader's classpath along with the sealed Derby jars. When the engine is booted, attempting to boot the services causes the sealing exception to be thrown. This is not a problem when running the test from jars because only derbyTesting.jar is made available to the old classloader, so there is not a sealing exception.
I think the thing to do is to create a custom ClassLoader that will only load classes from org.apache.derbyTesting, and then make this the parent of oldClassLoader, so that classes from org.apache.derbyTesting are loaded from the classes directory, and all other classes are loaded from the old jars when running the phases of the test with oldClassLoader. Despite my best efforts to subclass URLClassLoader to do this, I could not get it to cooperate. I'll come back to this at a later date, but am not planning on investigating it further at this time.
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: https://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.3.0
>
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
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-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1746?page=comments#action_12430281 ]
Rick Hillegas commented on DERBY-1746:
--------------------------------------
I'm afraid I'm a bit confused about what to do with these patches:
---------------- Trunk Patch -----------------------------
After I apply this patch to the trunk, I see the following diffs in the 10_1_10_2 test:
702a703
> ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx,7
707 del
< complete caseVersionCheck - passed true
707a708
> complete caseVersionCheck - passed false
1462 del
< END - PASS - phase SOFT UPGRADE
1462a1463
> END - FAIL - phase SOFT UPGRADE
2166a2168
> ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx,7
2171 del
< complete caseVersionCheck - passed true
2171a2173
> complete caseVersionCheck - passed false
2953 del
< END - PASS - phase UPGRADE
2953a2955
> END - FAIL - phase UPGRADE
Test Failed.
*** End: Upgrade_10_1_10_2 jdk1.4.2_08 2006-08-24 09:12:23 ***
I think that the lines beginning with ",APP,DERBY655T2," are new diffs added by this patch. It seems that this patch is making the results dirtier rather than cleaner.
In addition, I don't think we should be running a test called 10_1_10_2 in the trunk. We should be running some other tests, perhaps 10_1_to_Current and 10_2_to_Current in the trunk. Perhaps 10_1_10_2 becomes the basis for 10_1_to_Current.
--------------- 10.2 Patch --------------------------
Right now 10_1_10_2 runs cleanly in the 10.2 branch. After I apply this patch, I see the following diffs in the 10.2 branch:
702a703
> ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx,7
2166a2168
> ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx,7
Test Failed.
*** End: Upgrade_10_1_10_2 jdk1.4.2_08 2006-08-24 09:22:45 ***
It seems that some additional steps need to be taken before this patch can be applied to the 10.2 branch. Do we know what those are?
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: http://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.1.0
>
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
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-1746) upgrade tests should start using 10.1.3
released builds
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren closed DERBY-1746.
-------------------------------------
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: https://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.3.1.4
>
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff, svn_external
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495809 ]
Myrna van Lunteren commented on DERBY-1746:
-------------------------------------------
I think, this is now a mute point - or it's fixed by Dan (by converting the test).
However, we should now to remove the svn:externals dependency on the for 10.1, or, better still, to automatically add an svn;externals into our trunk for 10.3.1.0 ... etc...
Thoughts?
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: https://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Myrna van Lunteren
> Priority: Minor
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Andrew McIntyre (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496052 ]
Andrew McIntyre commented on DERBY-1746:
----------------------------------------
Myrna,
svn:externals expects only directories to be mapped. The jars in the jars repository aren't being used for anything else, and they were put there to facilitate upgrade testing in the first place. If it makes more sense to only have the derby.jars there, perhaps we should just remove everything but the derby.jars.
If it turns out that somebody is using the jars in the jars tree for some other purpose, or the community feels it makes sense to keep the full set of release jars in the repository for some other reason, than maybe it makes more sense to just check the derby jars for upgrade testing directly into the trunk and not use svn:externals. Then new releases can continue to be checked into the trunk, and branches will always be created with the appropriate set of upgrade jars for testing.
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: https://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Myrna van Lunteren
> Priority: Minor
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff, svn_external
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DERBY-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren reassigned DERBY-1746:
-----------------------------------------
Assignee: (was: Myrna van Lunteren)
I'm unassigning myself. As far as I can tell, the steps I made in my patch were the right thing to do. I haven't had a chance to look at this more.
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: https://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.3.0
>
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
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] Updated: (DERBY-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1746?page=all ]
Rick Hillegas updated DERBY-1746:
---------------------------------
Urgency: Normal (was: Urgent)
Degrading the urgency of this bug. Both 10.1 versions are reasonable starting points for upgrade and I would not let this issue block the release.
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: http://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.1.0
>
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
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-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1746?page=comments#action_12430342 ]
Daniel John Debrunner commented on DERBY-1746:
----------------------------------------------
I would actually say that we should test in the upgrade suite upgrading from *all* released versions of 10.1, not just the latest.
Maybe the setup is not ready for that, but it should be a goal of the 10.3 upgrade code. The scripts I originally wrote were designed to be flexible about the old and the new versions, thus one could test upgrading from:
10.1.2.x to 10.1.3.x
or
10.0.x.x to 10.1.3.x
or
10.1.3.x to 10.2.x.y
and the test would just check the right stuff.
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: http://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.1.0
>
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
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] Assigned: (DERBY-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren reassigned DERBY-1746:
-----------------------------------------
Assignee: Myrna van Lunteren
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: https://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff, svn_external
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495814 ]
Myrna van Lunteren commented on DERBY-1746:
-------------------------------------------
Also, I've done some experimenting, but the converted junit tests only need derby.jar of the old releases, but I can't get svn:externals give me just one file - it seems to want an entire directory.
when I tried to have it point to just derby.jar it gave me an error like so:
Fetching external item into 'tools\testing\derby\10.1.1.0\derby.jar'
svn: REPORT request failed on '/repos/asf/!svn/vcc/default'
svn:
Cannot replace a directory from within
Suggestions?
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: https://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Myrna van Lunteren
> Priority: Minor
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff, svn_external
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1746) upgrade tests should start using
10.1.3 released builds
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1746?page=comments#action_12430508 ]
Rick Hillegas commented on DERBY-1746:
--------------------------------------
I have now tried to apply this patch as follows:
cd tools/testing
svn propedit svn:externals . (editting the 10.1 version to be 10.1.3.1)
cd ../..
svn update
ant clobber
ant all
When I run the Upgrade_10_1_10_2 test I get pages of diffs and the following exception:
2956 add
> java.lang.ExceptionInInitializerError
> Caused by: java.lang.SecurityException: sealing violation: can't seal package org.apache.derby.iapi.services.crypto: a
lready loaded
Would appreciate advice on what I am doing wrong.
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: http://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.1.0
>
> Attachments: DERBY-1746_102_20060823.diff, DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn - 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for DERBY-655:
> 703d702
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> 2168d2166
> < ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx, 7
> It would be nice if the final build for 10.2 would include an updgrade test master created using 10.1.3, And same is true for the trunk.
--
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