RFR: 8212630: jtreg/gc/logging/TestMetaSpaceLog.java failed with Agent timed out

Thomas Schatzl thomas.schatzl at oracle.com
Mon Jun 3 09:17:50 UTC 2019

On Fri, 2019-05-31 at 20:37 -0400, Kim Barrett wrote:
> > On May 31, 2019, at 1:04 AM, Leonid Mesnik <
> > leonid.mesnik at oracle.com> wrote:
> > 
> > > [...]
> > Please note that this test is always executed with all GCs
> > specified even if specific GC is set using jtreg options. It
> > doesn't harm for single test but increase wasting time if many
> > tests use this approach. 
> > 
> > BTW If test is not GC specific then it might just pick GC from
> > jtreg command-line. It might be no sense to run it with all GCs
> > explicitly each time.
> I think what you are suggesting is this:
> http://cr.openjdk.java.net/~kbarrett/8212630/open.01
> and depend on running the test with various different GCs selected by
> the outer test driver (like mach5) to provide coverage.  I think for
> the current mach5 CI configuration, that would (currently) mean, for
> this test, default (G1) in tier1 and explicit G1 and others in tier2
> or tier3.
> I guess that's okay.

The test will now fail with ZGC (at least it does locally, when rung
with -vmoption:-XX:+UseZGC) which is afaik also run in CI, and needs to
be excluded in addition to Epsilon. Same with Shenandoah.


More information about the hotspot-gc-dev mailing list