Derby 10.3.1.0 Beta - summary testreport

1585 suitesAll: org.apache.derbyTesting.functionTests.tests.lang.ProcedureInTriggerTest

jvm1.4: []
jvm1.5: [lin32]
jvm1.6: []

10.2.2.1
10.2.2.0
10.2.1.7
10.2.1.6

1750 derbyall: stress/stress.multi

jvm1.4: [zone3]
jvm1.5: []
jvm1.6: []

...running last checks via final.sql
...timed out trying to kill all testers, ....

JIRA-2066 suitesAll: org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest: - signature[9]

jvm1.4: [w2000]
jvm1.5: []
jvm1.6: []

The DDM object 0x1232 is not supported. The connection has been terminated%

2290 lang/logStream.java:

jvm1.4: [vista]
jvm1.5: []
jvm1.6: []

10.2.2.1

2434 suitesAll:org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCHarnessJavaTest:

jvm1.4: [vista]
jvm1.5: [vista w2000 w2003]
jvm1.6: [vista w2000 w2003]

JIRA-2871 org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest: New JIRA?

jvm1.4: []
jvm1.5: [hpux]
jvm1.6: []

testXATransactionTimeout (org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest) org.apache.derby.client.am.XaException: XAER_PROTO : Error executing a XAResource.commit(), server returned XAER_PROTO.

The following are NOT Derby failures.Not counted above!

compatibility: Lib-paths for older Derby revisions not set up on Windows platforms.
-99?NoJIRA - signature[1]
-99?NoJIRA - signature[2]

jvm1.6: [vista w2000 w2003 winxp]

%Attempted 'embedded vs. network client' tests: 9, OK: 0, Failed: 9, Time: % seconds%
Attempted 'server - network client' tests: 324, OK: 0, Failed: 324, Time: % seconds%
Comment: Lib-paths for older Derby revisions not set up (Windows ...)

suitesAll/Upgrade: Lib-paths for older Derby revisions not set up on hpux.
org.apache.derbyTesting.functionTests.tests.upgradeTests....

jvm1.5: [hpux]

DERBY-1789 storemore:
store/TestDurabilityProperty.java
See comment from Sunitha Kambhampati - [08/Sep/06 04:33 PM ]: "... more of a performance test ...". Could then occur on a zones rig! Moving to "NOT Derby failures".

jvm1.4: []
jvm1.5: []
jvm1.6: [zones]

> FAIL -- derby.system.durability=test mode seems to be broken.
> -- In this mode one would expect that inserts with autocommit off and on would be in the same range as syncs are not happening but the difference here seems to be more than the approximate estimated range.
> -- Also comparing the time taken to do the inserts without this property set seems to be in the same range as with this property set.
> -- Please note this test times inserts and approximate estimates were considered to report this observation.