RFR: 7903746: jtreg tests run extremely slow on some environments due to hostname lookups [v2]

Jaikiran Pai jpai at openjdk.org
Tue Jul 9 08:13:47 UTC 2024


On Wed, 3 Jul 2024 11:00:29 GMT, Mark Sheppard <msheppar at openjdk.org> wrote:

>> @msheppar Is this worth a P4 followup RFE against InetAddress?
>
> 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.

-------------

PR Review Comment: https://git.openjdk.org/jtreg/pull/204#discussion_r1669965592


More information about the jtreg-dev mailing list