8321925: sun/security/mscapi/KeytoolChangeAlias.java fails with "Alias <246810> does not exist"

[sendaoYan]

Hi,

Clean backport of JDK-8321925. Only change the testcase, the change has been verified, the risk is low.

Thanks,
-sendao

---

Progress

• JDK-8321925 needs maintainer approval
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8321925: sun/security/mscapi/KeytoolChangeAlias.java fails with "Alias <246810> does not exist" (Bug - P3 - Approved)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk21u-dev.git pull/419/head:pull/419
$ git checkout pull/419

Update a local copy of the PR:
$ git checkout pull/419
$ git pull https://git.openjdk.org/jdk21u-dev.git pull/419/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 419

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk21u-dev/pull/419.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

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

[openjdk]

@sendaoYan 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:

8321925: sun/security/mscapi/KeytoolChangeAlias.java fails with "Alias <246810> does not exist"

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[openjdk]

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

[openjdk]

⚠️ @sendaoYan This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

[mlbridge]

Webrevs

• 01: Full - Incremental (4fdd7c80)
• 00: Full (e440478f)

[sendaoYan]

/approval request Clean backport of JDK-8321925. Only change the testcase, the change has been verified, the risk is low.

[openjdk]

@sendaoYan
8321925: The approval request has been created successfully.

[bridgekeeper]

@sendaoYan This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

[sendaoYan]

Hi,
/approval request Clean backport of JDK-8321925. Only change the testcase, the change has been verified, the risk is low.

[openjdk]

@sendaoYan
8321925: Approval has already been requested and approved.

[sendaoYan]

/integrate

[openjdk]

@sendaoYan
Your change (at version 4fdd7c8) is now ready to be sponsored by a Committer.

[sendaoYan]

/integrate

[openjdk]

@sendaoYan
Your change (at version 4fdd7c8) is now ready to be sponsored by a Committer.

[TheRealMDoerr]

/sponsor

[openjdk]

Going to push as commit bddd6a7.

[openjdk]

@TheRealMDoerr @sendaoYan Pushed as commit bddd6a7.

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

[sendaoYan]

/sponsor

Thanks.