The test failed on Solaris-sparc64 in Promotion testing of JDK7u40_b34 with this error message:
com.sun.jdi.connect.VMStartException: VM initialization failed for: /export/local/aurora/sandbox/java/re/jdk/7u40/promoted/all/b34/binaries/solaris-sparcv9/jre/bin/sparcv9/java -d64 -server -Xmixed -XX:+UseConcMarkSweepGC -Xdebug -Xrunjdwp:transport=dt_socket,address=jtg-t2000-11:42830,suspend=y nsk.jdi.ObjectReference._bounds_.bounds001a -verbose -arch=solaris-sparcv9 -waittime=5 -debugee.vmkind=java -transport.address=dynamic -debugee.vmkeys=-d64 -server -Xmixed -XX:+UseConcMarkSweepGC -pipe.port=42829
at com.sun.tools.jdi.AbstractLauncher$Helper.launchAndAccept(AbstractLauncher.java:192)
at com.sun.tools.jdi.AbstractLauncher.launch(AbstractLauncher.java:132)
at com.sun.tools.jdi.SunCommandLineLauncher.launch(SunCommandLineLauncher.java:235)
at nsk.share.jdi.Binder.localDefaultLaunchDebugee(Binder.java:264)
at nsk.share.jdi.Binder.bindToDebugeeNoWait(Binder.java:181)
at nsk.share.jdi.Binder.bindToDebugee(Binder.java:236)
at nsk.share.jdi.Debugee.prepareDebugee(Debugee.java:511)
at nsk.jdi.ObjectReference._bounds_.bounds001.run(bounds001.java:75)
at nsk.jdi.ObjectReference._bounds_.bounds001.main(bounds001.java:61)
It looks like the actual error message have been truncated.
There is a core file in the results directory.
Priority justification:
Impact: Medium, timeout
Likelihood: Low, happened once, test has succeeded many times since.
Workaround: Meduim, unknown.
ILW = MLM => P4
Link to failure: http://vmsqe-app.russia.sun.com/surl/1B
Link to test history: http://vmsqe-app.russia.sun.com/surl/1C
Matching rule:
RULE nsk/jdi/ObjectReference/_bounds_/bounds001 Exception nsk.share.Failure: Caught exception while starting debugee VM:
com.sun.jdi.connect.VMStartException: VM initialization failed for: /export/local/aurora/sandbox/java/re/jdk/7u40/promoted/all/b34/binaries/solaris-sparcv9/jre/bin/sparcv9/java -d64 -server -Xmixed -XX:+UseConcMarkSweepGC -Xdebug -Xrunjdwp:transport=dt_socket,address=jtg-t2000-11:42830,suspend=y nsk.jdi.ObjectReference._bounds_.bounds001a -verbose -arch=solaris-sparcv9 -waittime=5 -debugee.vmkind=java -transport.address=dynamic -debugee.vmkeys=-d64 -server -Xmixed -XX:+UseConcMarkSweepGC -pipe.port=42829
at com.sun.tools.jdi.AbstractLauncher$Helper.launchAndAccept(AbstractLauncher.java:192)
at com.sun.tools.jdi.AbstractLauncher.launch(AbstractLauncher.java:132)
at com.sun.tools.jdi.SunCommandLineLauncher.launch(SunCommandLineLauncher.java:235)
at nsk.share.jdi.Binder.localDefaultLaunchDebugee(Binder.java:264)
at nsk.share.jdi.Binder.bindToDebugeeNoWait(Binder.java:181)
at nsk.share.jdi.Binder.bindToDebugee(Binder.java:236)
at nsk.share.jdi.Debugee.prepareDebugee(Debugee.java:511)
at nsk.jdi.ObjectReference._bounds_.bounds001.run(bounds001.java:75)
at nsk.jdi.ObjectReference._bounds_.bounds001.main(bounds001.java:61)
It looks like the actual error message have been truncated.
There is a core file in the results directory.
Priority justification:
Impact: Medium, timeout
Likelihood: Low, happened once, test has succeeded many times since.
Workaround: Meduim, unknown.
ILW = MLM => P4
Link to failure: http://vmsqe-app.russia.sun.com/surl/1B
Link to test history: http://vmsqe-app.russia.sun.com/surl/1C
Matching rule:
RULE nsk/jdi/ObjectReference/_bounds_/bounds001 Exception nsk.share.Failure: Caught exception while starting debugee VM: