Fwd: Re: JTReg tests results on other ports
Jonathan Gibbons
jonathan.gibbons at oracle.com
Wed Sep 28 13:18:58 PDT 2011
For langtools, all the tests should pass all the time in any mode. It's
that simple, and we've worked hard to get to that point :-)
If the apt tests are failing, that would indicate a problem with what
you are testing -- i.e. the Mac build.
-- Jon
On 09/28/2011 01:06 PM, Henri Gomez wrote:
> When I use -s , langtool part for apt failed ;(
>
> I'm using jtreg-4.1-bin-b03_11_jul_2011.zip
>
>
> /Users/henri/Documents/jenkins/data/DROP_DIR/jtreg/linux/bin/jtreg
> -jdk:/Library/Java/JavaVirtualMachines/1.7.0.jdk/Contents/Home/ -s
> -ignore:quiet -v:summary test/tools
> FAILED: tools/apt/Basics/apt.sh
> FAILED: tools/apt/Basics/print.sh
> FAILED: tools/apt/Compile/compile.sh
> FAILED: tools/apt/Discovery/discovery.sh
> FAILED: tools/apt/mirror/declaration/AnnoMirror.java
> FAILED: tools/apt/mirror/declaration/AnnoTypeDecl.java
> FAILED: tools/apt/mirror/declaration/AnnoTypeElemDecl.java
> FAILED: tools/apt/mirror/declaration/AnnoVal.java
> FAILED: tools/apt/mirror/declaration/ClassDecl.java
> FAILED: tools/apt/mirror/declaration/ConstExpr.java
> FAILED: tools/apt/mirror/declaration/ConstructorDecl.java
> FAILED: tools/apt/mirror/declaration/EnumDecl.java
> FAILED: tools/apt/mirror/declaration/FieldDecl.java
> FAILED: tools/apt/mirror/declaration/GetAnno.java
>
>
>
> 2011/9/28 Jonathan Gibbons<jonathan.gibbons at oracle.com>:
>> On 09/28/2011 12:34 PM, Henri Gomez wrote:
>>> What are the jtreg usual parameters ?
>> For langtools, the minimal usual parameters are
>>
>> -s -ignore:quiet -v:summary test/
>>
>> -s
>> use samevm mode (runs most tests in the same JVM, instead of each test in
>> its own JVM)
>>
>> -ignore:quiet
>> a few remaining tests use @ignore; this option tells jtreg to ignore
>> these tests
>>
>> -v:summary
>> generate one line of output per test run;
>> this is good when running the tests from the command line
>> use -v:summary,nopass if you just want to know about failed/error results
>>
>> test/
>> Run all the tests (this is a path to a folder, so may be langtools/test
>> depending on your current directory)
>>
>> Personally, I always use -w and -r to override the default locations of the
>> work and report directory, using something like
>> -w build/jtreg/work -r build/jtreg/report
>>
>> Also, for langtools, set assertion options:
>> -ea:com.sun.tools... -esa
>>
>>
>> New:
>>
>> With jtreg 4.1 b03, you can replace "-s" (samevm mode) with "-agentvm"
>> (agentvm mode). AgentVM mode is "like samevm mode, but better". This allows
>> you to run tests concurrently, in separate JVMs. Specify the number with
>> -concurrency:N. Last time I tried this on my relatively new MacBook Pro, I
>> could run all the langtools tests in 2-3 minutes. :-) See
>> http://blogs.oracle.com/jjg/entry/jtreg_update1 for more details.
>>
>>
>> ----
>>
>> Separately, if anyone is building/debugging *just* langtools, you can build
>> just the langtools repository, and then use something like
>> -jdk:RECENT-JDK -Xbootclasspath/p:LANGTOOLS/build/classes.jar
>>
>> This saves having to build the entire JDK every time you edit langtools.
>>
>> -- Jon
>>
More information about the macosx-port-dev
mailing list