RFR: 7904152: jtreg tests fail with openjdk 25

[Christian Stein]

On Fri, 13 Feb 2026 06:44:02 GMT, Vladimir Petko <vpetko at openjdk.org> wrote:

> The policy tests try to set the Security manager on the command-line causing the following error:
> 
> java.lang.Error: A command line option has attempted to allow or enable the Security Manager. Enabling a Security Manager is not supported.
>        at java.lang.System.initPhase3([java.base at 25.0.2](mailto:java.base at 25.0.2)/System.java:1969)
> 
> The last supported JDK that allows setting the security manager is 21, so I have added `JDK21HOME` in line with other JDK-specific variables. 
> The alternative is to name the variable JDK23HOME as the security manager was disabled in openjdk-24[1]
> 
> [1] https://openjdk.org/jeps/486

Thanks for addressing this, Vladimir.

Adding `JDK21HOME` makes sense in general. So, does adding `JDK25HOME`. Please enhance this change set for 25.

Please also add both environment variables in the GitHub Action workflow configuration, like shown here: https://github.com/openjdk/jtreg/pull/313/changes#diff-faff1af3d8ff408964a57b2e475f69a6b7c7b71c9978cccc8f471798caac2c88 - I'll update PR 313 once this change here is integrated.

doc/building.md line 114:

> 112: 
> 113: Some tests depend on specific versions of JDK being available, specified
> 114: by the following variables: `JDK8HOME`, `JDK9HOME`, `JDK14HOME`, `JDK18HOME`, `JDK21HOME`.

Could be a list?
Suggestion:

by the following variables:
- `JDK8HOME`
- `JDK9HOME`
- `JDK14HOME`
- `JDK18HOME`
- `JDK21HOME`
- `JDK25HOME`

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

PR Comment: https://git.openjdk.org/jtreg/pull/315#issuecomment-3895697854
PR Review Comment: https://git.openjdk.org/jtreg/pull/315#discussion_r2803029309