Re: Client/Server compatibility testing

[Kathey Marsden]

Suran Jayathilaka wrote:
I disabled the 
org.apache.derbyTesting.functionTests.tests.jdbc4.UnsupportedVetter 
test which was causing the hang in the 10.4 source and built the 
testing jar and ran suites.All.

Thanks Suran for running these tests. I am still a little torn about 
whether to file a new issue about this hang or just keep it with 
DERBY-4053.  Even though the symptoms are signature DERBY-4053, it 
really is sort of a new regression that we get the hang so reliably with 
mixed version client/server.  Do others have an opinion on whether this 
should be filed as  anew bug?


Tests run: 10523,  Failures: 56,  Errors: 12

After analyzing the results with Kathey, one issue was filed at 
https://issues.apache.org/jira/browse/DERBY-4180.

A failure was seen in DboPowersTest, which was not reproducible when 
run alone.
47) 
testReEncrypt(org.apache.derbyTesting.functionTests.tests.jdbcapi.DboPowersTest)junit.framework.AssertionFailedError:
 
D:\projects\derby10.5rc2-test\cli4-srv5-4\system\singleUse\oneuse1f\seg0\o3e1.dat

        at 
org.apache.derbyTesting.junit.DropDatabaseSetup.removeDir(DropDatabaseSetup.java:130)
        at 
org.apache.derbyTesting.junit.DropDatabaseSetup.removeDir(DropDatabaseSetup.java:128)
        at 
org.apache.derbyTesting.junit.DropDatabaseSetup.access$000(DropDatabaseSetup.java:35)

        at 
org.apache.derbyTesting.junit.DropDatabaseSetup$1.run(DropDatabaseSetup.java:105)
        at java.security.AccessController.doPrivileged(Native Method)
        at 
org.apache.derbyTesting.junit.DropDatabaseSetup.removeDirectory(DropDatabaseSetup.java:102)

        at 
org.apache.derbyTesting.junit.DropDatabaseSetup.removeDirectory(DropDatabaseSetup.java:98)
        at 
org.apache.derbyTesting.junit.DropDatabaseSetup.removeDatabase(DropDatabaseSetup.java:91)
        at 
org.apache.derbyTesting.junit.TestConfiguration$3.tearDown(TestConfiguration.java:598)

        at junit.extensions.TestSetup$1.protect(TestSetup.java:22)
        at junit.extensions.TestSetup.run(TestSetup.java:25)
        at 
org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
        at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)

        at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
        at junit.extensions.TestSetup.run(TestSetup.java:25)
        at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
        at junit.extensions.TestSetup$1.protect(TestSetup.java:21)

        at junit.extensions.TestSetup.run(TestSetup.java:25)
        at 
org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
        at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
        at junit.extensions.TestSetup$1.protect(TestSetup.java:21)

        at junit.extensions.TestSetup.run(TestSetup.java:25)

Thanks!
Suran
  





On Mon, Apr 20, 2009 at 8:10 PM, Suran Jayathilaka <suran...@gmail.com 
<mailto:suran...@gmail.com>> wrote:

    When running suites.All against 10.4 client and 10.5.1.1 RC2
    server, the tests hang after
    ConnectionMethodsTest.testConnectionIsValid().

    This happened both times I ran the suite using 2 different test
    setup folders.

    Kathey, shall we analyze this on IRC today?
    Thanks!
    Suran