RFR(xs): 8161552: Test issue: VM init failed: GC triggered before VM initialization completed. Try increasing NewSize, current value 768K.
zoltan.majo at oracle.com
Thu Jul 21 08:30:17 UTC 2016
On 07/21/2016 10:26 AM, Dmitry Fazunenko wrote:
> Hi Zoltan,
> Thanks for reviewing!
> The tests are currently quarantined in jdk9/dev, but not in jdk9/hs yet.
> To test them properly I prefer to integrate through the jdk9/hs
> I will either wait for sync or un-quarantine as a separate change.
thank you for the clarification! What you're proposing is reasonable.
To make sure we don't forget to un-quarantine those test, could you
please file a sub-task for un-quarantining? We could then use the JBS ID
of that sub-task to push the un-quarantining change.
> On 21.07.2016 10:49, Zoltán Majó wrote:
>> Hi Dima,
>> thank you for taking care of this issue, your changes look generally
>> good to me. But I would be interested in whether you plan to
>> un-quarantine the two tests that originally failed:
>> If yes, can you maybe do that with the current changeset? If not, can
>> you please explain why?
>> Thank you!
>> Best regards,
>> On 07/20/2016 07:01 PM, Dmitry Fazunenko wrote:
>>> I'm looking for a couple of reviewers for a simple fix of two tests.
>>> The tests check some basic assertions when VM is started with max
>>> heap size set to some small values.
>>> The tests work almost everywhere, but there are cases when with
>>> -Xmx2M GC triggered before VM initialization completed.
>>> 2M is valid but extremely small max heap size. Cases of usages such
>>> small heap are rather theoretical than practical.
>>> To fix the problem I made the tests weaker, the cases setting max
>>> heap to 2M are removed.
>>> Testing: locally + RBT
More information about the hotspot-gc-dev