RFR (S): 8068026: [TESTBUG] Check for -client in gc/g1/TestHumongousCodeCacheRoots.java

Thomas Schatzl thomas.schatzl at oracle.com
Tue Jan 20 13:13:01 UTC 2015

On Tue, 2015-01-20 at 12:53 +0000, Lindenmaier, Goetz wrote:
> Hi Thomas,
> yes, it would be better if the jtreg framework could sort it out right away.
> But in this case, you would get two very similar tests, one of which 
> would be executed always, thus not saving anything.

Not sure what you mean here: currently, the test starts three VMs, ie.
the main VM that executes two other VMs where one always fails if there
is no client VM.

With the proposed change, jtreg will only start the VMs that are
supported, i.e. either one or two.

>  Except for having
to adapt two tests if there is a change needed.

Since the meat of the code (TestHumongousCodeCacheRootsHelper) would be
in a shared class and the shells just forwarding to that, I do not see a
problem with such changes.
I would imagine that the code would get cleaner and smaller, because the
setup to execute the TestHumongousCodeCacheRootsHelper would go away.

> Also, it's been pushed in the meantime.
> http://hg.openjdk.java.net/jdk9/hs-gc/hotspot/rev/8dfd8b00c7f1

I did not notice that, somehow overlooked that - it was still on my
todo-list :) Sorry.

> Should I still improve the test?

It would be nice, but not that important I guess. I created an RFE at
https://bugs.openjdk.java.net/browse/JDK-8069343 to work on if you want.


More information about the hotspot-dev mailing list