8367583: sun/security/util/AlgorithmConstraints/InvalidCryptoDisabledAlgos.java fails after JDK-8244336

[satyenme]

Backporting JDK-8367583: sun/security/util/AlgorithmConstraints/InvalidCryptoDisabledAlgos.java fails after JDK-8244336. Fixes buggy test. Ran GHA Sanity Checks and fixed test directly to confirm passing. Patch is clean. Backporting for parity with Oracle.

---

Progress

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

Issue

• JDK-8367583: sun/security/util/AlgorithmConstraints/InvalidCryptoDisabledAlgos.java fails after JDK-8244336 (Bug - P2 - Approved)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 4355

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back ssubramaniam! 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]

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

8367583: sun/security/util/AlgorithmConstraints/InvalidCryptoDisabledAlgos.java fails after JDK-8244336

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.

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

[openjdk]

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

[openjdk]

⚠️ @satyenme 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

• 02: Full - Incremental (6b12eb8b)
• 01: Full (e99506ce)
• 00: Full (5d367b8c)

[satyenme]

/approval request for backport of JDK-8367583: sun/security/util/AlgorithmConstraints/InvalidCryptoDisabledAlgos.java fails after JDK-8244336

Motivation: With this change, we provide additional test coverage without changing any functionality (so minimal risk). Change will bring openjdk closer to matching oracle.

Risk: Low. Ran GHA Sanity Checks and adjusted test. Patch is clean. Change has been accepted by Oracle (and test is currently failing).

[openjdk]

@satyenme
8367583: The approval request has been created successfully.

[openjdk]

@satyenme Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information.

[satyenme]

Sorry about that, accidentally pushed commit to this branch - reverted to only include the relevant patch

[satyenme]

/integrate

[openjdk]

Going to push as commit 35ad4d5.

[openjdk]

@satyenme Pushed as commit 35ad4d5.

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