Skip to content

8388142: [8u] Path to PreferredKey.java exclusion is wrong - #841

Closed
adamfarley wants to merge 1 commit into
openjdk:masterfrom
adamfarley:unexclude_preferredkey_test
Closed

8388142: [8u] Path to PreferredKey.java exclusion is wrong#841
adamfarley wants to merge 1 commit into
openjdk:masterfrom
adamfarley:unexclude_preferredkey_test

Conversation

@adamfarley

@adamfarley adamfarley commented Jul 13, 2026

Copy link
Copy Markdown

Test was excluded due to issue that was later fixed.

Also, the unexclusion refers to the old file location, which no longer exists, so the exclusion isn't excluding anything.



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
  • JDK-8388142 needs maintainer approval

Issue

  • JDK-8388142: [8u] Path to PreferredKey.java exclusion is wrong (Bug - P4 - Approved)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 841

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

Using diff file

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

Using Webrev

Link to Webrev Comment

Test was excluded due to issue that was later fixed.

Also, the unexclusion refers to the old file location, which no
longer exists, so the exclusion isn't excluding anything.

Signed-off-by: Adam Farley <adfarley@ibm.com>
@bridgekeeper

bridgekeeper Bot commented Jul 13, 2026

Copy link
Copy Markdown

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

openjdk Bot commented Jul 13, 2026

Copy link
Copy Markdown

@adamfarley This change now passes all automated pre-integration checks.

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

8388142: [8u] Path to PreferredKey.java exclusion is wrong

Reviewed-by: andrew

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 17 new commits pushed to the master branch:

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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@gnu-andrew) but any other Committer may sponsor as well.

➡️ 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 openjdk Bot added the rfr Pull request is ready for review label Jul 13, 2026
@adamfarley

Copy link
Copy Markdown
Author

/approval 8388142 request Request to unexclude a test because all issues it is linked to are resolved. Also, the test moved since it was excluded, and the exclusion no longer excludes anything.

@openjdk

openjdk Bot commented Jul 13, 2026

Copy link
Copy Markdown

@adamfarley
8388142: The approval request has been created successfully.

@openjdk openjdk Bot added the approval Requires approval; will be removed when approval is received label Jul 13, 2026
@mlbridge

mlbridge Bot commented Jul 13, 2026

Copy link
Copy Markdown

Webrevs

@adamfarley

Copy link
Copy Markdown
Author

The only test failures I'm seeing are in CAInterop.java, which is not associated with this test as far as I can tell.

@gnu-andrew

Copy link
Copy Markdown
Member

As noted on the bug, only two of the four referenced issues are actually resolved. You seem to be misreading the bug being resolved as it being resolved everywhere, but you need to look at the fix version. If it is higher than the version concerned (in this case, 8) you need to look for backport issues to see if it has been backported to older versions. Or just use git log --grep= on a repository checkout.

I think the main issue here is that the exclusion is redundant. The culprit for this is JDK-8245477 which moved the test nearly six years ago and never corrected the ProblemList.txt. As it has effectively been removed from the exclude list for all that time, I don't really see an issue with just removing it now. But the the test does exist and is currently failing, which should be resolved by #832

@gnu-andrew gnu-andrew left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks ok. Note that you should wait for a review before requesting approval.

@gnu-andrew

Copy link
Copy Markdown
Member

/approve yes

@openjdk

openjdk Bot commented Jul 28, 2026

Copy link
Copy Markdown

@gnu-andrew
8388142: The approval request has been approved.

@openjdk openjdk Bot removed the approval Requires approval; will be removed when approval is received label Jul 28, 2026
@gnu-andrew

Copy link
Copy Markdown
Member

The title of the PR needs to be changed to "8388142: [8u] Path to PreferredKey.java exclusion is wrong"

@adamfarley adamfarley changed the title 8388142: Unexcluding X509KeyManager/PreferredKey.java 8388142: [8u] Path to PreferredKey.java exclusion is wrong Jul 29, 2026
@openjdk openjdk Bot added the ready Pull request is ready to be integrated label Jul 29, 2026
@adamfarley

Copy link
Copy Markdown
Author

/integrate

@openjdk openjdk Bot added the sponsor Pull request is ready to be sponsored label Jul 29, 2026
@openjdk

openjdk Bot commented Jul 29, 2026

Copy link
Copy Markdown

@adamfarley
Your change (at version 77693a6) is now ready to be sponsored by a Committer.

@gnu-andrew

Copy link
Copy Markdown
Member

/sponsor

@openjdk

openjdk Bot commented Jul 30, 2026

Copy link
Copy Markdown

Going to push as commit aa3f9de.
Since your change was applied there have been 17 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk Bot added the integrated Pull request has been integrated label Jul 30, 2026
@openjdk openjdk Bot closed this Jul 30, 2026
@openjdk openjdk Bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Jul 30, 2026
@openjdk

openjdk Bot commented Jul 30, 2026

Copy link
Copy Markdown

@gnu-andrew @adamfarley Pushed as commit aa3f9de.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

2 participants