-
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
8279941: sun/security/pkcs11/Signature/TestDSAKeyLength.java fails when NSS version detection fails #10346
Conversation
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
@shipilev 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 12 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. ➡️ To integrate this PR with the above commit message to the |
Thank you! Any other reviews needed, or this one is enough? |
One should be enough. Just a trivial change. |
Thanks! /integrate |
Going to push as commit cddd6de.
Your commit was automatically rebased without conflicts. |
The test helpers try to identify NSS version by parsing the relevant
.so
files (!) looking for "Version: ..." string. This fails at least on Ubuntu 22.04, where the NSS does not have any version-identifiable strings. In this case, the test "detects" version as0.0
and then fails. After brief discussion in the bug, the best fix is to ignore0.0
as well.Additional testing:
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10346/head:pull/10346
$ git checkout pull/10346
Update a local copy of the PR:
$ git checkout pull/10346
$ git pull https://git.openjdk.org/jdk pull/10346/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10346
View PR using the GUI difftool:
$ git pr show -t 10346
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10346.diff