Fwd: Re: RFR (XXS): 8132334: [TESTBUG] gc/metaspace/TestCapacityUntilGCWrapAround.java Compilation failed
dmitry.fazunenko at oracle.com
Thu Jul 30 09:58:29 UTC 2015
A trivial fix is still waiting for reviewers...
Comments: w/a for known jtreg issue described:
-------- Forwarded Message --------
Subject: Re: RFR (XXS): 8132334: [TESTBUG]
gc/metaspace/TestCapacityUntilGCWrapAround.java Compilation failed
Date: Tue, 28 Jul 2015 21:07:50 +0300
From: Dmitry Fazunenko <dmitry.fazunenko at oracle.com>
To: Kim Barrett <kim.barrett at oracle.com>
CC: hotspot-gc-dev <hotspot-gc-dev at openjdk.java.net>
On 28.07.2015 4:40, Kim Barrett wrote:
> On Jul 27, 2015, at 9:12 PM, Dmitry Fazunenko <dmitry.fazunenko at oracle.com> wrote:
>> On 27.07.2015 21:49, Kim Barrett wrote:
>>> On Jul 24, 2015, at 12:23 PM, Dmitry Fazunenko <dmitry.fazunenko at oracle.com> wrote:
>>>> Hi everyone,
>>>> Can I have reviews for the trivial change that must fix the compilation problem?
>>>> Comments: In some circumstances jtreg doesn't see wb classes if they weren't built explicitly.
>>> Under what circumstances does this occur? I see other tests that look very similar to the pre-change version of this test - what makes this test so special?
>> I don't have an answer. I just heard about such problem, but I didn't find the bug. Might be because it's not filed yet. The hypothesis is the concurrency might cause such effect.
> Without an understanding of why this change is needed here but not
> elsewhere, I'm concerned that we're either
> 1. papering over one instance of a more widespread problem, or
> 2. not really solving the problem with this test after all.
I found the jtreg bug:
It's about 3 years old and still un-triaged, so I won't expect it will
be fixed soon.
But the problem could be easily worked around and this change does it.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the hotspot-gc-dev