Derby 10.3.1.4 RC4 - summary testreport

Release candidate 10.3.1.4 was created 2007-08-01 (svn revision 561794) and testing was started 2007-08-02.

Testing was done under jvm1.6 with individual tests (derbyall subsuites) and derbyall and suitesAll. Under jvm1.5 and jvm1.4 derbyall and suitesAll was run.

Results pr jvm-version can be found under jvm1.4, jvm1.5, jvm1.6.
Summary of additional tests are found here.

Here is a table with a summary of failures found including comments on these:

Counting the number of distinct errors, total number of error occurences and platforms used in 10.3.1.4 testing we find:

 

10.2.2.0

10.3.1.0

10.3.1.1

10.3.1.2

10.3.1.3

10.3.1.4

Distinct
errors

2

6

10

7

4

5

1.4

0 / 0 / 18

4 / 4 / 21

6 / 23 / 21

3 / 3 / 21

2 / 2 / 21

5 / 7 / 21

1.5

2 / 3 / 19

3 / 5 / 22

6 / 30 / 22

6 / 8 / 22

3 / 5 / 22

2 / 6 / 22

1.6

0 / 0 / 18

1 / 3 / 21

3 / 29 / 21

2 / 7 / 21

4 / 7 / 21

2 / 4 / 21

Legend: Distinct errors / Sum errors / Number of platforms.
suitesAll results for 1.5 / hpux are missing in the report. Manual inspection shows no issues except known infrastructure problems on upgrade test.

The complete Large DataVolume test, consisting of DOTS/ATCJ4(previously called ATCJ2), backup, restore, aggregate and consistency testing was run for 48 hrs on a database with ATCJ4 tables of 8, 300, 232 million tuples, using 184 GB raw disk space. No issues seen.

JDBC 3.0 Compatibility Test Suite (CTS) (part of the J2EE TCK) was run on a number of different platforms. See SunCTS for details.

The compatibility test (CompatibilityCombinations/JDBC) was only run on SunOS x86 5.10_64. No issues seen.

A LongTermTest was started on version 10.3.1.1. See LongTermTest for details. No derby-failures seen. But after 80 hours an increase in CPU- and memory-usage was noticed without a good explanation. Also some exceptions were raised when requesting locks.

Report generated: Thu Aug 06 11:45:00 MEST 2007

JIRA/Id

JVM/OS

Comment

Seen in XX

 

 

 

 

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

jvm1.4: [sles x 2]
jvm1.5: [linN-1,sles]
jvm1.6: [lin]

Not able to create trigger due to an open ResultSet

10.3.1.3
10.3.1.2
10.3.1.1
10.3.1.0
10.2.2.1
10.2.2.0
10.2.1.7
10.2.1.6

1750 stress/stress.multi

jvm1.4: [sol32, sparc]

 

 

2290 lang/logStream.java:

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

logStream reports 'derby.log has content ? false'

10.3.1.3
10.2.2.1
10.3.1.0
10.3.1.1
10.3.1.2

2456

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

Reoccurrence of closed 2456?
1)ImportExportProcedureTestjunit.framework.AssertionFailedError: extinout\t1.dat
at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDir(DropDatabaseSetup? .java:129)<

 

2899 .JDBCHarnessJavaTest: reoccurrence of 2434.

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

 

10.3.1.3
10.2.2.1
10.3.1.0
10.3.1.1
10.3.1.2

The following are NOT Derby failures.Not counted above!

???? derbynetmats/DerbyNet

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

derby.drda.host=xxxFILTERED_HOSTNAMExxx
derby.drda.host=127.0.0.1

10.3.1.3
10.3.1.1

???? derbynetmats/DerbyNet

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

com.ibm.db2.jcc.c.SqlException: java.net.ConnectException :
Error opening socket to server xxxFILTERED_HOSTNAMExxx on port 1527 with message : Connection refused
derby.drda.host=xxxFILTERED_HOSTNAMExxx
derby.drda.host=127.0.0.1
derby.drda.traceAll=false
derby.drda.traceAll=true

10.3.1.3
10.3.1.1

Apache Derby 10.3 test summaries

10.3 release Testing:
Platform testing, Buddy testing, Application testing.

Conclusion

We do not regard any of the found problems as showstoppers for a release.

-- OleSolberg - 07 Aug 2007