JDK-6913186 : a number of vm tests failed against jdk 5.0 with HS 16 nightly build
  • Type: Bug
  • Component: vm-legacy
  • Sub-Component: jvmpi
  • Affected Version: 5.0u22
  • Priority: P3
  • Status: Closed
  • Resolution: Not an Issue
  • OS: solaris
  • CPU: sparc
  • Submitted: 2009-12-24
  • Updated: 2010-04-02
  • Resolved: 2010-01-20
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
5.0-poolResolved
Related Reports
Relates :  
Description
See comments

Comments
EVALUATION Closed as not-a-bug.
20-01-2010

EVALUATION This JDK1.5.0_22 release train uses HSX-16.1. JVM/PI was removed in HSX-10-B13/JDK6_Update4: 4914266 5/3 Remove JVMPI in Dolphin/JDK7/Java7 so these tests are not valid in this JDK1.5.0_22 release train. I'm not sure if this bug should be closed as "not a bug" or if it will be used to update the testbase. I'm leaving the bug open for now.
05-01-2010

EVALUATION http://jqa.ireland.sun.com/export/home0/results/1.5.0_22/hsx-12-21/issues/4418568/Test4418568.jtr This test failed with the following message: ERROR: JVMPI, an experimental interface, is no longer supported. Please use the supported interface: the JVM Tool Interface (JVM TI). Error occurred during initialization of VM -Xrun library failed to init: jvmdi_tool http://jqa.ireland.sun.com/export/home0/results/1.5.0_22/hsx-12-21/issues/4478849/Test4478849.jtr This test failed with the following message: ERROR: JVMPI, an experimental interface, is no longer supported. Please use the supported interface: the JVM Tool Interface (JVM TI). Error occurred during initialization of VM -Xrun library failed to init: test http://jqa.ireland.sun.com/export/home0/results/1.5.0_22/hsx-12-21/issues/4514097/PingPong.jtr This test failed with the following message: result: Failed. Execution failed: exit code 1 However, the test title is: title=JVMPI_MONITOR_WAITED value returned is wrong Fixed in JDK1.3.1_09 Fixed in JDK1.4.1_05 which indicates that this is a JVM/PI test so I'm guessing there is an agent failure message like the previous ones that did not get captured. http://jqa.ireland.sun.com/export/home0/results/1.5.0_22/hsx-12-21/issues/4614956/Test4614956.jtr This test failed with the following message: result: Failed. Execution failed: exit code 1 However, the test title is: title=4614956: enablev006: JVMPI_EVENT_OBJECT_ALLOC request crashes Server VM 5053217: VM segv's running jvmti/jvmpi profiler Fixed in JDK1.4.2_06 5069985:Fix for 4614956 fails on Solaris9 for 142 06 b01 Fixed in JDK1.4.2_06 Respin b02 which indicates that this is a JVM/PI test so I'm guessing there is an agent failure message like the previous ones that did not get captured. http://jqa.ireland.sun.com/export/home0/results/1.5.0_22/hsx-12-21/issues/4657650/Test4657650.jtr This test failed with the following messages: Test crashed, failed result: Failed. Execution failed: exit code 1 However, the test title is: title=threadstart002: suspend/resume fails with intermediate DeleteGlobalRef call Fixed in JDK1.4.0_01 - respin which indicates that this is a JVM/PI test. The agent level suspend/resume API in the JDK1.4.0 era is in JVM/PI.
05-01-2010