Looking ahead: proposed Hg forest consolidation for JDK 10

Jonathan Gibbons jonathan.gibbons at oracle.com
Wed Oct 12 15:52:24 UTC 2016

On 10/12/16 12:16 AM, Lindenmaier, Goetz wrote:

>>> > >We find it difficult to keep the jtreg runner in sync with our
>>> > >current version of jdk9, especially as we have two of them (We
>>> > >test openJdk and SAP JVM 9, and within SAP JVM 9 hotspot and
>>> > >jdk often differ in a few builds.)
>>> > >I would appreciate if the runner could be included in the
>>> > >root/test directory.
>> >
>> >I'm not quite sure what you are referring to by the jtreg runner.
> I mean the code inhttp://hg.openjdk.java.net/code-tools/jtreg


What sort of troubles have you been having here?  The intent is to provide
one version of jtreg that works for all supported JDK versions. Currently,
the intent is that jtreg supports running tests on all versions back to 
JDK 5.

That being said, jtreg does advance slowly, and there is a value to identify
the minimum required version of jtreg in the test/TEST.ROOT file for each
repository that contains jtreg tests. If nothing else, you could use 
that value
to help select a specific version of jtreg, assuming you build/provide
multiple versions.

I do accept that folk working on the jigsaw/jake forest will sometimes have
to use the latest version of jtreg (i.e. tip, not the latest tagged 
version) but
that is part of living and working on "the bleeding edge", and which does
not sound like your situation.

In short, I think the cost of the logistics to keep jtreg in the main 
JDK forest,
including the need to backport changes, would far outweigh any benefits,
especially when there is related concern about the overall size of an 
consolidated repo.

-- Jon

More information about the jdk9-dev mailing list