jonathan.gibbons at oracle.com
Tue Aug 20 12:55:33 PDT 2013
It sounds like you have insufficient @build directives and that some of
your library classes are being implicitly compiled (into the wrong place)
On 08/19/2013 10:03 PM, Henry Jen wrote:
> I try to move a test for Pattern.splitAsStream() into
> test/java/util/regex because that is where is should be based on
> convention. The test is now currently several layers under
> test/java/util/stream as initially developed in part of lambda testng tests.
> The move is not straightforward because it makes use of stream test
> framework which has to be included in bootclasspath.
> I added @library tag, and hopefully it picks up bootclasspath.dir
> setting from TEST.properties located in
> test/java/util/stream/bootlib/TEST/properties as that seems to be how
> stream tests works.
> This partially works. What I mean by that is, if I try to run regex test
> from a clean state, the bootclasspath is not picked up and the test
> failed as show in attached PatternTest.jtr.failed as you can see in the
> rerun section(a nice feature, BTW).
> However, if I run a stream test first and keep the JT* working folder,
> the test passes. Attached is the patch file, and you can reproduce this
> with following steps after apply attached JDK-8016846 for the test,
> $ cd jdk
> $ jtreg -v test/java/util/regex #failed
> $ jtreg -v
> $ jtreg -v test/java/util/regex #succeeded
> or combine above two steps into one also work,
> $ jtreg -v
> test/java/util/regex #succeeded
> Do I miss any option here or this is not really supported?
More information about the jtreg-use