Two JCK vm tests are failing when performing random read/write on double/float array:

javasoft.sqe.tests.vm.dastore.dastore001.dastore00101.dastore00101
javasoft.sqe.tests.vm.fastore.fastore001.fastore00101.fastore00101

jtg-s210:[242]% uname -a
SunOS jtg-s210 5.8 Generic_109291- customer  sun4m sparc SUNW,SPARCstation-5
jtg-s210:[243]% psrinfo -v
Status of processor 0 as of: 05/30/00 19:24:34
  Processor has been on-line since 05/24/00 17:34:13.
  The sparc processor operates at 170 MHz,
	and has a sparc floating point processor.

To Reproduce:
=============
1. Extract fastore00101.ksh and dastore00101.ksh from the attached jar files:

jtg-s210:[263]% fastore00101.ksh -client
+ SWITCH=-client
+ TESTBASE=/net/ultraowl.eng/export/ultraowl1/javatb/testbase
+ JCK=/net/ultraowl.eng/export/ultraowl1/javatb/testbase/src/JCK-runtime-13rc2
+ CLASSPATH=.:/net/ultraowl.eng/export/ultraowl1/javatb/testbase/src/JCK-runtime-13rc2/classes:/net/ultraowl.eng/export/ultraowl1/javatb/testbase/src/JCK-runtime-13rc2/javatest.jar
+ PATH=/usr/java1.2/bin:/bin
+ export CLASSPATH PATH
+ java -client -Djava.security.policy=/net/ultraowl.eng/export/ultraowl1/javatb/testbase/src/JCK-runtime-13rc2/lib/jck.policy -verify javasoft.sqe.tests.vm.fastore.fastore001.fastore00101.fastore00101
+ rc=97
+ echo 97
97
+ return 97

jtg-s210:[268]% dastore00101.ksh -client
+ SWITCH=-client
+ TESTBASE=/net/ultraowl.eng/export/ultraowl1/javatb/testbase
+ JCK=/net/ultraowl.eng/export/ultraowl1/javatb/testbase/src/JCK-runtime-13rc2
+ CLASSPATH=.:/net/ultraowl.eng/export/ultraowl1/javatb/testbase/src/JCK-runtime-13rc2/classes:/net/ultraowl.eng/export/ultraowl1/javatb/testbase/src/JCK-runtime-13rc2/javatest.jar
+ PATH=/usr/java1.2/bin:/bin
+ export CLASSPATH PATH
+ java -client -Djava.security.policy=/net/ultraowl.eng/export/ultraowl1/javatb/testbase/src/JCK-runtime-13rc2/lib/jck.policy -verify javasoft.sqe.tests.vm.dastore.dastore001.dastore00101.dastore00101
+ rc=97
+ echo 97
97
+ return 97

This problem is limited to sun4m machines ONLY. The tests will run fine when changing to compiler2. 


  xxxxx@xxxxx   2000-05-30

N/A

exclude javasoft/sqe/tests/vm/fastore/fastore001/fastore00101/fastore00101 randomRead
exclude javasoft/sqe/tests/vm/dastore/dastore001/dastore00101/dastore00101 randomRead

by excluding these two methods the test passes.  If the CanonicalizeNodes flag is turned off the test passes without exclusion of the above methods in mixed mode.


Running the tests in -Xcomp generates an exception before it ever gets to the above methods.

Exception in thread "main" java.lang.IllegalArgumentException: Illegal Load factor: 0.75
        at java.util.HashMap.<init>(HashMap.java:140)
        at java.util.HashMap.<init>(HashMap.java:158)
        at java.util.jar.Attributes.<init>(Attributes.java:54)
        at java.util.jar.Attributes.<init>(Attributes.java:44)
        at java.util.jar.Manifest.<init>(Manifest.java:38)
        at java.util.jar.JarFile.getManifest(JarFile.java:145)
        at sun.misc.URLClassPath$JarLoader.getClassPath(URLClassPath.java:609)
        at sun.misc.URLClassPath.getLoader(URLClassPath.java:223)
        at sun.misc.URLClassPath.getResource(URLClassPath.java:133)
        at java.net.URLClassLoader$1.run(URLClassLoader.java:192)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:297)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:290)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:286)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:253)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313)
still investigating see bug: 4335360
  xxxxx@xxxxx   2000-06-01

Robert or Srdjan, please use the doit script in /net/sqesvr/vsn/GammaBase/Bugs/4342163. Note that you must rlogin to  jtg-s210 in order to repro the bug. You may also be able to use ionpulse if it is up and running. Since it is sparc10 and runs a little fater.
  xxxxx@xxxxx   2000-06-01

This is a duplicate bug as in 4342148. It should be fixed with that putback in b2. Note, that the fix also fixes the -Xcomp problem mentioned above.
  xxxxx@xxxxx   2000-06-05