failures running jdk/test/java/dyn tests

[John Rose]

On Jan 11, 2011, at 6:37 PM, Stephen Bannasch wrote:

> At 5:48 PM -0800 1/11/11, John Rose wrote:
>> You can run with jtreg directly like this:
>> $ jtreg -jdk:$JAVA7X_HOME test/java/dyn/
>> $ jtreg -jdk:$JAVA7X_HOME test/java/dyn/InvokeDynamicPrintArgs.java
>> 
>> ...and so on.
> 
> Do the java/dyn/InvokeDynamicPrintArgs.java tests pass on your build?

Yes.

> What is $JAVA7X_HOME defined as?

It's my latest stable build of bleeding-edge JDK7, at $DAVINCI/sources/build/bsd-i586/j2sdk-image/.

> I don't have JAVA7X_HOME defined but I think I should get the same effect using this option:
> 
>  -jdk:build/bsd-amd64/j2sdk-image

Yes.

> Doesn't jtreg also need to send these options to the jvm it is testing:
> 
>  -XX:+UnlockExperimentalVMOptions -XX:+EnableInvokeDynamic

No.  Those flags are mentioned in the jtreg test file itself:
 * @run main/othervm -XX:+UnlockExperimentalVMOptions -XX:+EnableInvokeDynamic

>> Sometimes, when working with an incremental rebuild of the jdk stuff I do it this way:
>> $ jtreg -vmoption:-Xbootclasspath/p:$DAVINCI/patches/netbeans/meth/dist/meth.jar -jdk:$JAVA7X_HOME test/java/dyn
> 
> I haven't been using netbeans and don't have the following directory:
> 
>  /patches/netbeans/meth/dist
> 
> Is that created with netbeans?

Yes.  From the command line, just go into "meth" and type "ant jar" or just "ant".

> Are you using netbeans to compile and test mlvm?

Incrementally; I'm using the makefiles to do  full builds.  AFAIK nobody but me is using the netbeans projects.

-- John