-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8345134: Test sun/security/tools/jarsigner/ConciseJarsigner.java failed: unable to find valid certification path to requested target #23001
Conversation
…failed: unable to find valid certification path to requested target set the date as -1M in the cert to prevent the future cert from being used.
👋 Welcome back myankelev! A progress list of the required criteria for merging this PR into |
@myankelev 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:
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 162 new commits pushed to the
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 (@wangweij) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
@myankelev The following label will be automatically applied to this pull request:
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. |
Webrevs
|
@myankelev 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. |
There are many certificates created in this test. Why are only these 2 lines updated? |
changed to apply to all certificates if |
/integrate |
@myankelev |
/sponsor |
Going to push as commit a0f7982.
Your commit was automatically rebased without conflicts. |
@wangweij @myankelev Pushed as commit a0f7982. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Changed the gencert, so the certificate is now initialised to be with a start time of -1M. This prevents a potential error with the certificate not yet being valid.
Similar solution to this pull request
Have tested the test 6000 times for stability and all have passed.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23001/head:pull/23001
$ git checkout pull/23001
Update a local copy of the PR:
$ git checkout pull/23001
$ git pull https://git.openjdk.org/jdk.git pull/23001/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 23001
View PR using the GUI difftool:
$ git pr show -t 23001
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23001.diff
Using Webrev
Link to Webrev Comment