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)" <ji...@apache.org> on 2007/05/16 22:54:16 UTC
[jira] Resolved: (DERBY-1746) upgrade tests should start using
10.1.3 released builds
[ 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.