RFR: 7903746: jtreg tests run extremely slow on some environments due to hostname lookups [v2]
Mark Sheppard
msheppar at openjdk.org
Tue Jul 9 09:57:44 UTC 2024
On Tue, 9 Jul 2024 08:10:54 GMT, Jaikiran Pai <jpai at openjdk.org> wrote:
>> It probably is worth raising an issue. I think I raised some years back. IIRC the thinking at the time was the hostname is dynamically configurable so it is necessary to obtain the most current setting (but then again so are IP addresses and they are extensively cached). Nonetheless, it is worth further discussion as an enhancement
>
> Hello Mark,
>
>> LazyHostNameLookup infers a lookup deferred to the latest possible moment While
> CachedHostName would convey a more appropriate semantics.
>
> I have now updated the PR to use the term "Cached" instead of "Lazy". No other changes. Tests continue to pass.
cheers JP, thanks for considering the suggestion
-------------
PR Review Comment: https://git.openjdk.org/jtreg/pull/204#discussion_r1670171128
More information about the jtreg-dev
mailing list