I ran derbyall with the jars on the following platforms:
- AIX, using ibm 1.4.2 'Classic' jvm
---------------
Classic VM (build 1.4.2, J2RE 1.4.2 IBM AIX build ca1420-20040626 (JIT enabled: jitc))
---------------
- RHEL3.0 Linux, using ibm's 64 bit 1.4.2 jvm
---------------
IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20050609
(JIT enabled)
J9VM - 20050524_1742_LHdSMr
JIT - r7_level20050518_1803)
(JIT enabled)
J9VM - 20050524_1742_LHdSMr
JIT - r7_level20050518_1803)
---------------
- RHEL3.0 Linux, Sun's jdk1.5 jvm
---------------
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_04-b05, mixed mode)
---------------
I found only the following known issues:
- the jvm/master update problem with tools/importExport.java and ibm142
- intermittent failures in stress.multi and dataSourcePermissions_net.java
- hang in cacheService.unit (DERBY-625) with the 64 bit jvm
and some jvm/test related issues with the 64 bit jvm.
So...
+1
Myrna
On 10/26/05, Deepa Remesh <[EMAIL PROTECTED]> wrote:
I ran derbyall with the jars in db-derby-10.1.2.0-lib.zip on Windows
XP, j9_foundation VM in IBM WCTME 5.7. No new failures.
2 known failures:
jdbcapi/nullSQLText.java (This test uses a procedure with server-side
JDBC which is not supported on this platform)
store/oc_rec3.java (This looks like an intermittent failure.
Discussion is at
http://www.nabble.com/lang-wisconsin.sql-t369871.html#a1043391)
My vote +1
