RFR: 8356102: TestJcmdOutput, JcmdWithNMTDisabled and DumpSharedDictionary hs/tier1 tests fail on static-jdk [v2]
David Holmes
dholmes at openjdk.org
Tue May 13 07:38:52 UTC 2025
On Mon, 12 May 2025 21:56:46 GMT, Jiangli Zhou <jiangli at openjdk.org> wrote:
> The jdk/internal/misc/VM/RuntimeArguments.java test fails due the additional command-line option
Interesting and very frustrating. It seems there are potentially other flags that could get passed already that would cause the same kind of failure.
This really is not something that tests should need to be aware of. And to be honest the fact that -Dcompiler.jdk even exists and solves this problem is somewhat of a fortuitous accident (it was added way, way back to allow testing with JRE's that did not contain all the JDK tools).
Doe a static JDK image not implicitly contain all the tools, if you invoked them directly rather than via their custom launchers? Or are they stripped out unless explicitly created as part of that image? I'm just wondering if there is a more direct way for JdkToolFinder to work with static images?
-------------
PR Comment: https://git.openjdk.org/jdk/pull/25018#issuecomment-2875381470
More information about the hotspot-runtime-dev
mailing list