failures running dyn tests with jtreg on mlvm

John Rose john.r.rose at Oracle.com
Mon Jan 31 18:07:20 PST 2011


That's better.  The assertion failure is fixed here:
  http://hg.openjdk.java.net/jdk7/hotspot/hotspot/log?rev=7010180

It has to get pushed to jdk7 and then bsd-port.  It got fixed directly in hotspot-comp and therefore does not appear in an mlvm patch.

-- John

On Jan 31, 2011, at 6:00 PM, Stephen Bannasch wrote:

> At 5:35 PM -0800 1/31/11, John Rose wrote:
>> On Jan 31, 2011, at 3:50 PM, Stephen Bannasch wrote:
>> 
>>> I'm getting new failures running the dyn tests in mlvm.
>>> 
>>> Seems like the  -XX:+UnlockExperimentalVMOptions -XX:+EnableMethodHandles are being passed into junit.
>> 
>> Oops, that should work.  For some reason, the runtime for MHs now entangles Indy.  It's not obvious to me what's goingwrong.
>> 
>> As a workaround, you can add these arguments to jtreg:
>> jtreg -XX:+UnlockExperimentalVMOptions -XX:+EnableInvokeDynamic ...
>> 
>> Then all the tests should pass.
> 
> InvokeDynamicPrintArgs generated a fatal error
> 
> $ jtreg -XX:+UnlockExperimentalVMOptions -XX:+EnableInvokeDynamic -jdk:build/bsd-amd64/j2sdk-image -v:verbose jdk/test/java/dyn                      
> runner starting test: java/dyn/ClassValueTest.java
> runner finished test: java/dyn/ClassValueTest.java
> Passed. Execution successful
> runner starting test: java/dyn/InvokeDynamicPrintArgs.java
> runner finished test: java/dyn/InvokeDynamicPrintArgs.java
> Failed. Unexpected exit from test [exit code: 134]
> runner starting test: java/dyn/InvokeGenericTest.java
> runner finished test: java/dyn/InvokeGenericTest.java
> Passed. Execution successful
> runner starting test: java/dyn/JavaDocExamplesTest.java
> runner finished test: java/dyn/JavaDocExamplesTest.java
> Passed. Execution successful
> runner starting test: java/dyn/MethodHandlesTest.java
> runner finished test: java/dyn/MethodHandlesTest.java
> Passed. Execution successful
> Test results: passed: 4; failed: 1
> 
> 
> 
> more details:
> 
> command: main -XX:+UnlockExperimentalVMOptions -XX:+EnableInvokeDynamic indify.Indify --verify-specifier-count=3 --transitionalJSR292=false --expand-properties --classpath ${test.classes} --java test.java.dyn.InvokeDynamicPrintArgs --check-output
> reason: User specified action: run main/othervm -XX:+UnlockExperimentalVMOptions -XX:+EnableInvokeDynamic indify.Indify --verify-specifier-count=3 --transitionalJSR292=false --expand-properties --classpath ${test.classes} --java test.java.dyn.InvokeDynamicPrintArgs --check-output
> elapsed time (seconds): 1.297
> ----------System.out:(22/944)----------
> # To suppress the following error report, specify this argument
> # after -XX: or in .hotspotrc:  SuppressErrorAt=/methodOop.cpp:697
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  Internal Error (/Users/stephen/dev/java/src/mlvm/sources/hotspot/src/share/vm/oops/methodOop.cpp:697), pid=91347, tid=4434546688
> #  assert(_adapter == NULL) failed: init'd to NULL
> #
> # JRE version: 7.0
> # Java VM: OpenJDK 64-Bit Server VM (20.0-b06-fastdebug mixed mode bsd-amd64 compressed oops)
> # An error report file with more information is saved as:
> # /Users/stephen/dev/java/src/mlvm/sources/JTwork/scratch/hs_err_pid91347.log
> #
> # If you would like to submit a bug report, please visit:
> #   http://java.sun.com/webapps/bugreport/crash.jsp
> #
> VM option '+UnlockExperimentalVMOptions'
> VM option '+EnableInvokeDynamic'
> VM option '+UnlockExperimentalVMOptions'
> VM option '+EnableInvokeDynamic'
> Current thread is 4434546688
> Dumping core ...
> ----------System.err:(10/800)----------
> patching test/java/dyn/InvokeDynamicPrintArgs.main(L)V
> 16:invokestatic 6 INDY_nothing()L;...; 19:invokevirtual 7 => invokedynamic 409:InvokeDynamic[0, 407]
> 22:invokestatic 8 INDY_bar()L;...; 28:invokevirtual 10 => invokedynamic 416:InvokeDynamic[1, 414]
> 31:invokestatic 11 INDY_bar2()L;...; 39:invokevirtual 10 => invokedynamic 418:InvokeDynamic[1, 417]
> 42:invokestatic 13 INDY_baz()L;...; 51:invokevirtual 17 => invokedynamic 421:InvokeDynamic[2, 420]
> 54:invokestatic 18 INDY_foo()L;...; 59:invokevirtual 20 => invokedynamic 412:InvokeDynamic[0, 411]
> patching test/java/dyn/InvokeDynamicPrintArgs.bsm(LLL)L
> 24:invokestatic 82 MH_printArgs()L => ldc 399:MethodHandle[6, 398]
> patching test/java/dyn/InvokeDynamicPrintArgs.bsm2(LLLL)L
> 47:invokestatic 82 MH_printArgs()L => ldc 399:MethodHandle[6, 398]
> result: Failed. Unexpected exit from test [exit code: 134]
> 
> 
> test result: Failed. Unexpected exit from test [exit code: 134]
> _______________________________________________
> mlvm-dev mailing list
> mlvm-dev at openjdk.java.net
> http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev



More information about the mlvm-dev mailing list