db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mamta Satoor <msat...@gmail.com>
Subject Re: Compatibility test runs?
Date Tue, 14 Sep 2010 21:54:48 GMT
Hi Rick,

thanks for the 2 attachements. I modified them for my environment and
tried and it appears that the database "wombat" never gets created. I
am not sure what is wrong. I do have test.printDebug set to true and
so I am seeing that test is getting run. It seems to be stuck in
recreateDB method trying to create wombat. In my dir from where I am
running the test, I do not see any wombat dir getting created. I
wonder what is wrong. I will continue to debug but Rick do you see
something wrong? Thanks. I have attached my versions of runcompat and
compatibilitytest.properties


$ ./runcompat
.*** Properties -----------------------------------------
user.dir:          C:\p4clients\svnmain\client2\trunk\systest\out142
derby.system.home: C:\p4clients\svnmain\client2\trunk\systest\out142\system
realPropertyFile: compatibilitytest.properties
printDebug: true
showSysinfo: true
serverPort: 1527
testSuite: org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.
CompatibilitySuite
runEmbedded: true
runSrvrClnt: true
includeUpgrade: false
singleClient: null
singleClientVM: null
singleServer: null
singleServerVM: null
specialTestingJar: null
securityProperty: noSecurityManager
0: j16lib
j16lib: C:/p4clients/ntsoftware/ntsoftware/ibm16/jre/bin
10.0.2.1: C:/p4clients/releasedJars/jars/10.0.2.1 false
10.1.1.0: C:/p4clients/releasedJars/jars/10.1.1.0 false
10.2.2.0: C:/p4clients/releasedJars/jars/10.2.2.0 false
10.4.2.1: C:/p4clients/releasedJars/jars/10.4.2.1 true
10.6.1.0: C:/p4clients/releasedJars/jars/10.6.1.0 true
Trunk: C:/p4clients/svnmain/client2/trunk/jars/sane true
db2jcc_lib: C:/p4clients/ntsoftware/ntsoftware/jcc2.6
junit_jar: C:/p4clients/svnmain/client2/trunk/java/junit.jar
jce_jar: C:/p4clients/ntsoftware/ntsoftware/ibm131/jre/lib/ext/jce1_2_2.jar
jdbc2_0_stdext_jar:
C:/p4clients/svnmain/client2/trunk/tools/java/jdbc2_0-stdext.jar
test_jars: C:/p4clients/svnmain/client2/trunk/jars/sane\derbyTesting.jar:C:/p4clients/svnmain/client2/trunk/java/junit.jar:C:/p4clients/ntsoftware/ntsoftware/ibm131/jre/lib/ext/jce1_2_2.jar
--------------------------------------------------------
derbyCreatorJar:
C:/p4clients/svnmain/client2/trunk/jars/sane\derby.jar:C:/p4clients/svnmain/client2/trunk/jars/sane\derbynet.jar

+++ recreateDB
user.dir: C:\p4clients\svnmain\client2\trunk\systest\out142
Successfully deleted database dir
'C:\p4clients\svnmain\client2\trunk\systest\out142\wombat'
commandElements:
C:/p4clients/ntsoftware/ntsoftware/ibm16/jre/bin\..\bin\java
-Ddrb.tests.debug=true -Dderby.tests.trace=true -cp
C:/p4clients/svnmain/client2/trunk/jars/sane\derby.jar:C:/p4clients/svnmain/client2/trunk/jars/sane\derbynet.jar:C:/p4clients/svnmain/client2/trunk/jars/sane\derbyTesting.jar:C:/p4clients/svnmain/client2/trunk/java/junit.jar:C:/p4clients/ntsoftware/ntsoftware/ibm131/jre/lib/ext/jce1_2_2.jar
org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.CompatibilitySuite$Creator
wombat -noSecurityManager
envElements: CLASS_PATH=C:/p4clients/svnmain/client2/trunk/jars/sane\derby.jar:C:/p4clients/svnmain/client2/trunk/jars/sane\derbynet.jar:C:/p4clients/svnmain/client2/trunk/jars/sane\derbyTesting.jar:C:/p4clients/svnmain/client2/trunk/java/junit.jar:C:/p4clients/ntsoftware/ntsoftware/ibm131/jre/lib/ext/jce1_2_2.jar
proc = Runtime.getRuntime().exec(fullCmd,envElements,workingDir);


On Mon, Sep 13, 2010 at 12:04 PM, Rick Hillegas
<rick.hillegas@oracle.com> wrote:
> Hi Mamta,
>
> I am attaching two files which may be helpful:
>
> o runcompat - This is the master script which I use to run the compatibility
> tests. The setupTests script (not included) sets up the classpath to point
> at the Derby trunk jars; the script also creates a subdirectory called
> testRun and cd's to it.
>
> o compatibilitytest.properties - This is a set of properties for configuring
> the test run. The properties describe where the VMs and Derby versions live.
>
> Hope this is helpful,
> -Rick
>
> Mamta Satoor wrote:
>>
>> I ran following to get info on how to run the compatibility test
>> ant -buildfile testScript.xml -projecthelp
>>
>> It seems to currently only test 10.0 through 10.2 releases of network
>> server products. Is it just out of date and we need to change the
>> script to allow users to specify higher releases of products? Does
>> Ole's nightly tests only test network server/client combinations for
>> 10.0 through 10.2?
>>
>> thanks,
>> Mamta
>>
>> On Thu, Sep 9, 2010 at 3:18 PM, Myrna van Lunteren
>> <m.v.lunteren@gmail.com> wrote:
>>
>>>
>>> On Thu, Sep 9, 2010 at 2:02 PM, Mamta Satoor <msatoor@gmail.com> wrote:
>>>
>>>>
>>>> Hi,
>>>>
>>>> I am working on a jira DERBY-4786 which requires testing of different
>>>> versions of client and server. It appears that there is something
>>>> called CompatibilitySuite.java. Is that what I would be running to
>>>> test the compatibility between different versions? How do I run that
>>>> test? Will I be able to test different revisions of the same major
>>>> release, for instance, say client at revision 10.3.3.1 against server
>>>> at 10.3.1.4? Then, I need to add a test of my own to the compatibility
>>>> test suite to try shutdown between different versions of clients and
>>>> servers.
>>>>
>>>> thanks,
>>>> Mamta
>>>>
>>>>
>>>
>>> Hi Mamta,
>>>
>>> There's a CompatibilitySuite.java in
>>>
>>> java/testing/org/apache/derbyTesting/functionTests/tests/junitTests/compatibility.
>>> It has a README.html.
>>>
>>> Hope this helps.
>>> Myrna
>>>
>>>
>>
>>
>
>
> test.testSuite=org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.CompatibilitySuite
> # Optional, default false
> # test.printDebug=false
>
> # Optional, default false
> # test.showSysinfo=true
>
> # Optional, default false
> # test.includeUpgrade=true
> # Simply means the database files are NOT removed between server starts.
> # Observe that trunk should not be included when test.includeUpgrade=true.
>
> #############################
> # Server port to use: optional, default 1527
> test.serverPort=1527
> # Since  CompatibilitySuite and JDBCDriverTest only handles default..
> # Most tests are not yet ready for a non-default value.
>
> #############################
> # Jvms to be used for server and client side:
> # 'jvm.versions' tells how many. 'jvm.N=<descriptive_name>' defines
> # names of properties giving the full path to the actual jvms.
> jvm.versions=3
> # jvm.0=j13lib
> jvm.0=j14lib
> jvm.1=j15lib
> jvm.2=j16lib
>
> # j13lib=/export/home/rh161140/sw/java/j2sdk1_3_1_19/jre/lib
> #j14lib=/export/home/rh161140/sw/java/j2sdk1.4.2_12/jre/lib
> #j15lib=/export/home/rh161140/sw/java/jdk1.5.0_09/jre/lib
> #j16lib=/export/home/rh161140/sw/java/jdk1.6.0/jre/lib
> j14lib=/System/Library/Frameworks/JavaVM.framework/Versions/1.4/Home/bin
> j15lib=/System/Library/Frameworks/JavaVM.framework/Versions/1.5/Home/bin
> j16lib=/System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home/bin
>
> ##############################
> # Derby versions to be used for server and client side:
> #-----------------------------
> # 'derby.versions' how many. 'derby.versionN=<descriptive_name>' defines
> # names of properties giving the full path to the actual Derby libraries.
> derby.versions=6
> derby.version0=10.0.2.1
> derby.version1=10.1.1.0
> derby.version2=10.2.2.0
> derby.version3=10.4.2.1
> derby.version4=10.6.1.0
> derby.version5=Trunk
>
> #derby.versions=3
> #derby.version0=10.0.2.1
> #derby.version1=10.6.1.0
> #derby.version2=Trunk
>
> Trunk=/Users/rh161140/derby/mainline/trunk/jars/sane
> 10.0.2.1=/Users/rh161140/derby/upgradeReleases/10.0.2.1
> 10.1.1.0=/Users/rh161140/derby/upgradeReleases/10.1.1.0
> 10.1.2.0=/Users/rh161140/derby/upgradeReleases/10.1.2.0
> 10.1.3.1=/Users/rh161140/derby/upgradeReleases/10.1.3.1
> 10.2.2.0=/Users/rh161140/derby/upgradeReleases/10.2.2.0
> 10.2.2.1=/Users/rh161140/derby/upgradeReleases/10.2.2.1
> 10.3.3.0=/Users/rh161140/derby/upgradeReleases/10.3.3.0
> 10.4.2.1=/Users/rh161140/derby/upgradeReleases/10.4.2.1
> 10.5.3.0=/Users/rh161140/derby/upgradeReleases/10.5.3.0
> 10.6.1.0=/Users/rh161140/derby/upgradeReleases/10.6.1.0
>
> #-----------------------------
> # Which Derby versions are security enabled:
> 10.0.2.1_SA=false
> 10.1.1.0_SA=false
> 10.1.2.1_SA=false
> 10.1.3.1_SA=false
> 10.2.2.0_SA=false
> 10.2.2.1_SA=false
> 10.3.3.0_SA=true
> 10.4.2.1_SA=true
> 10.5.3.0_SA=true
> 10.6.1.0_SA=true
> Trunk_SA=true
>
> #-----------------------------
> # Specify security option string for security enabled version(s)
> test.securityOption=noSecurityManager
>
> #-----------------------------
> # Driver to use for 10.0.2.1(incubator version - no Derby provided driver):
> db2jcc_lib=/Users/rh161140/sw/db2jcc/lib
>
> #-----------------------------
> # Use a special testing jar? Optional
> # E.g. your own experimental:
> #
> test.derbyTestingJar=/home/testuser/Derby/testSandbox/trunk/jars/insane/derbyTesting.jar
>
> #-----------------------------
> # Use one single derby version server, optional:
> # test.singleServer=5
> # 5 for derby.version5, which in this example maps to Trunk
> #-----------------------------
> # Use one single jvm version server, optional:
> # test.singleServerVM=2
> # 2 for jvm.2, which in this example maps to j16lib
>
> #-----------------------------
> # Use one single derby version client, optional:
> # test.singleClient=5
> # for derby.version5, which in this example maps to Trunk
> ----------------------------
> # Use one single jvm version server, optional:
> # test.singleClientVM=2
> # 2 for jvm.2, which in this example maps to j16lib
>
> ##############################
> # Utilities...
> junit_jar=/Users/rh161140/sw/junit/junit.jar
> jce_jar=/Users/rh161140/sw/jce/jce1.2.2/lib/jce1_2_2.jar
> jdbc2_0_stdext_jar=/Users/rh161140/derby/mainline/trunk/tools/java/jdbc2_0-stdext.jar
>
>
>

Mime
View raw message