RFR (S): 8076995: gc/ergonomics/TestDynamicNumberOfGCThreads.java failed with java.lang.RuntimeException: 'new_active_workers' missing from stdout/stderr
derek.white at oracle.com
Wed Apr 22 16:30:35 UTC 2015
On 4/22/15 11:34 AM, Jon Masamitsu wrote:
> On 4/21/2015 1:56 PM, Derek White wrote:
>> Thanks Jon!
>> On 4/21/15 1:23 PM, Jon Masamitsu wrote:
>>> Thanks for fixing this.
>>> Fix looks good.
>>> What do you think about always making testDynamicNumberOfGCThread()
>>> check for the uniprocessor case (as opposed to passing in a flag to
>>> check it)?
>> This may not catch all of the failures. What I couldn't pin down was
>> why some 2, 3(!), or 4 core ARM machines would result in defaulting
>> ParallelGCThreads=1. Now these were embedded machines, with
>> potentially "odd" versions of linux, possibly with "odd" errata. Or
>> perhaps there was some dynamic differences between "installed" and
>> "on-line" cores.
>> In any case the safest test seemed to be to force ParallelGCThreads=1
>> and see if it works.
> I don't think I said it right. What I meant was that
> should always test both cases (emulate_uniprocessor true and false)
> instead of calling
> testDynamicNumberOfGCThread() twice, once with emulate_uniprocessor
> true and once
> with emulate_uniprocessor false. Was that what you responded to?
Ah, OK. Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the hotspot-gc-dev