8360416: Incorrect l10n test case in sun/security/tools/keytool/i18n.java

[justin-curtis-lu]

Please review this PR which is a backport of commit 5540a785 from the openjdk/jdk repository.

This is a test-only issue which removes an incorrect l10n test case.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8360416: Incorrect l10n test case in sun/security/tools/keytool/i18n.java (Bug - P4)

Reviewers

• Hai-May Chao (@haimaychao - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26431/head:pull/26431
$ git checkout pull/26431

Update a local copy of the PR:
$ git checkout pull/26431
$ git pull https://git.openjdk.org/jdk.git pull/26431/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 26431

View PR using the GUI difftool:
$ git pr show -t 26431

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26431.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back jlu! A progress list of the required criteria for merging this PR into jdk25 will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@justin-curtis-lu This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8360416: Incorrect l10n test case in sun/security/tools/keytool/i18n.java

Reviewed-by: hchao

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 6 new commits pushed to the jdk25 branch:

• 7b69679: 8362564: hotspot/jtreg/compiler/c2/TestLWLockingCodeGen.java fails on static JDK on x86_64 with AVX instruction extensions
• bf31e50: 8364089: JDK 25 RDP2 L10n resource files update
• 9fe2aa5: 8356587: Missing object ID X in pool jdk.types.Method
• ... and 3 more: https://git.openjdk.org/jdk/compare/e8f2cd8f3d5b5174200a987b2cdea13b151fc19f...jdk25

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the jdk25 branch, type /integrate in a new comment.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[openjdk]

@justin-curtis-lu The following label will be automatically applied to this pull request:

• security

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 00: Full (c25d6d1c)

[justin-curtis-lu]

@wangweij When you have the chance, are you able to review this issue you already reviewed in mainline. It is a test-only issue and eligible for backport to JDK25. TIA!

[kevinrushforth]

@justin-curtis-lu If you plan to integrate this, please do so before the RC build, which is on Aug 7.

[justin-curtis-lu]

Thanks for the review.
/integrate

[openjdk]

Going to push as commit 9bdf9eb.
Since your change was applied there have been 6 commits pushed to the jdk25 branch:

• 7b69679: 8362564: hotspot/jtreg/compiler/c2/TestLWLockingCodeGen.java fails on static JDK on x86_64 with AVX instruction extensions
• bf31e50: 8364089: JDK 25 RDP2 L10n resource files update
• 9fe2aa5: 8356587: Missing object ID X in pool jdk.types.Method
• ... and 3 more: https://git.openjdk.org/jdk/compare/e8f2cd8f3d5b5174200a987b2cdea13b151fc19f...jdk25

Your commit was automatically rebased without conflicts.

[openjdk]

@justin-curtis-lu Pushed as commit 9bdf9eb.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.