-
Bug
-
Resolution: Fixed
-
P4
-
6
-
b67
-
generic
-
generic
New INSTRUMENT_REGRESSION failures (from 2005.12.06)
java/lang/instrument/BootClassPath/BootClassPathTest.sh
This test failed due to a ClassNotFoundException (AgentSupport)
on Linux IA32 Client VM (machine otterpop). otterpop used a
local JDK copy. I suspect that otterpop has a bad copy of the
JDK from the 2005.12.01 run.
Update: The bad JDK copy on otterpop has been fixed.
Update: Now robodog is failing the test and otterpop failed the
test again. otterpop used a network mounted JDK this time
and Francis cleaned up the vmsqe days ago. I'm not sure
what is going on here.
Update: Francis has investigated this failure and does not
think it is related to a bad JDK copy. I've asked Robert
to look at this issue.
Update: On the 2005.12.08 run, this test failed on Solaris X86
Client VM (machine cyborrea), Solaris SPARC Client VM
(machine minifridge), Solaris X86 Server VM (machine
screamerhawk).
Update: Alan says warnings like the following appear to be the
cause of this test's failure mode:
Java HotSpot(TM) Client VM warning: Performance bug:
SystemDictionary lookup_count=6243 lookup_length=3805
average=0.609483 load=0.294351
java/lang/instrument/BootClassPath/BootClassPathTest.sh
This test failed due to a ClassNotFoundException (AgentSupport)
on Linux IA32 Client VM (machine otterpop). otterpop used a
local JDK copy. I suspect that otterpop has a bad copy of the
JDK from the 2005.12.01 run.
Update: The bad JDK copy on otterpop has been fixed.
Update: Now robodog is failing the test and otterpop failed the
test again. otterpop used a network mounted JDK this time
and Francis cleaned up the vmsqe days ago. I'm not sure
what is going on here.
Update: Francis has investigated this failure and does not
think it is related to a bad JDK copy. I've asked Robert
to look at this issue.
Update: On the 2005.12.08 run, this test failed on Solaris X86
Client VM (machine cyborrea), Solaris SPARC Client VM
(machine minifridge), Solaris X86 Server VM (machine
screamerhawk).
Update: Alan says warnings like the following appear to be the
cause of this test's failure mode:
Java HotSpot(TM) Client VM warning: Performance bug:
SystemDictionary lookup_count=6243 lookup_length=3805
average=0.609483 load=0.294351