Release 10.4.1.3 was created 2008-04-16 (svn revision 648739) and
testing was started 2008-04-18.
Testing was done under jvm1.6 with
suitesAll and derbyall plus jdbcapi
tests and the compatibility test. Under jvm1.5 and
jvm1.4 derbyall and suitesAll was
run.
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.4.1.3 testing we find:
|
|
10.2.2.0 |
10.2.2.1 |
10.3.1.0 |
10.3.1.1 |
10.3.1.2 |
10.3.1.3 |
10.3.1.4 |
10.3.2.1 |
10.4.1.0 |
10.4.1.1 |
10.4.1.2 |
10.4.1.3 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Distinct |
2 |
9 |
6 |
10 |
7 |
4 |
5 |
6 |
6 |
1 |
4 |
1 |
|
1.4 |
0 / 0 / 18 |
3 / 5 / 21 |
4 / 4 / 21 |
6 / 23 / 21 |
3 / 3 / 21 |
2 / 2 / 21 |
5 / 7 / 21 |
2 / 3 / 20 |
0 / 0 / 23 |
0 / 0 / 26 |
1 / 1 / 24 |
0 / 0 / 26 |
|
1.5 |
2 / 3 / 19 |
2 / 2 / 22 |
3 / 5 / 22 |
6 / 30 / 22 |
6 / 8 / 22 |
3 / 5 / 22 |
2 / 6 / 22 |
4 / 4 / 20 |
4 / 6 / 23 |
0 / 0 / 26 |
2 / 4 / 26 |
0 / 0 / 26 |
|
1.6 |
0 / 0 / 18 |
5 / 5 / 21 |
1 / 3 / 21 |
3 / 29 / 21 |
2 / 7 / 21 |
4 / 7 / 21 |
2 / 4 / 21 |
0 / 0 / 20 |
2 / 7 / 24 |
0 / 0 / 27 |
0 / 0 / 28 |
0 / 0 / 28 |
|
1.6-64 |
- / - / - |
- / - / - |
- / - / - |
- / - / - |
- / - / - |
- / - / - |
- / - / - |
- / - / - |
0 / 0 / 7 |
1 / 2 / 11 |
1 / 2 / 12 |
1 / 2 / 12 |
Legend: Distinct errors / Sum errors / Number of platforms.
JDBC 3.0 Compatibility Test Suite (CTS) (part of the J2EE TCK) was run on a number of different platforms. See SunCTS for details.
Report generated: Tuesday Apr 22 13:45:00 MEST 2008
|
1902
derbyall: |
jvm1.4: [] |
Hash Join ResultSet |
10.3.2.1 |
|
The following are test or infrastructure problems. Do not count above. |
|||
|
3529 replicationSuite: replicationTests.ReplicationRun_Local_StateTest_part1_1 |
jvm1.4: [] |
|
10.4.1.0 |
|
3632 replicationSuite: replicationTests.ReplicationRun_Local_StateTest_part2 |
jvm1.4: [sol-zone1 sol-zones w2003-64] |
|
10.4.1.2 |
We have noticed that some machines got into trouble with too
high CPU-load. We have not concluded yet if this was due to product,
test or environmental problems, but expect the latter to be true.
See also Apache
Derby community platform testing reports for 10.4.1.
I can recommend a positive vote!
-- Henri van de Scheur - 22 Apr 2008