jtreg and build question

[loc-en-dev]

Thanks Naoto.

I've downloaded jtreg and verified that I can use it to test changes
to Locale.java.

I have two more questions, if you don't mind.

1) jtreg takes about five minutes to run the 13 Locale tests, which
I'd like to run quickly as a sanity check.  I suspect there's a better
way to invoke it than the ways I have tried.  Currently I cd to the
root of my local jdk7 repo and try this

../jtreg/linux/bin/jtreg -jdk:build/linux-i586 test/java/util/Locale

or this

../jtreg/linux/bin/jtreg -jdk:build/linux-i586 -dir:test/java/util/Locale .

or this

cd test/java/util/Locale
~/openjdk/jtreg/linux/bin/jtreg -jdk:../../../../build/linux-i586 .

All report on the 13 tests I ran as well as the 3,000+ tests I
skipped.  I expect scanning all the tests is what's taking up all the
time.  There must be a way to restrict the scan to only one (or a few)
subdirectories.  Is there?

2) recompiling also takes a long time.  currently to build the
fastdebug target I need to start from the root makefile under
jdk/make.  I can build the 'all' target under jdk/java/make, but I'd
prefer to build everything with the same options.  Is there a
combination of location and target that is better for quick rebuilds?

On the other hand, Locale is such as basic class that it might be
better to just rebuild everything all the time.

What do the Sun i18n folks do?

Doug

On Mon, Dec 1, 2008 at 11:33 AM, Naoto Sato <Naoto.Sato at sun.com> wrote:
> Hi Doug,
>
> Thank you for bootstrapping the project!
>
> As to the test harness, I believe that you are referring to 'jtreg', which
> is now an open source project:
>
> http://openjdk.java.net/jtreg/
>
> Thanks,
> Naoto