-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
JDK-8296631 NSS tests failing on OL9 linux-aarch64 hosts #15644
Conversation
👋 Welcome back mpowers! A progress list of the required criteria for merging this PR into |
Webrevs
|
I will take a look. Thanks! |
double version = getNSSVersion(); | ||
if (version == 0.0 || version >= 3.55) { | ||
useSqlite(true); | ||
} |
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.
Instead of updating various tests with this block, how about doing this inside SecmodTest.initSecmod()?
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.
Such a change would apply NSS version number checks to TestNssDbSqlite
which currently doesn't have them. But wait! If TestNssDbSqlite
has been running for years on all NSS versions, then it should be safe to make sqlite the default for all tests.
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.
Yes, for new NSS releases, it should be safe to set sqlite to true by default. The tests which relies on sqlite like TestNssDbSqlite
can always call useSqlite(true) regardless of default.
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.
@valeriepeng Thanks for the review! I'll set sqlite to true by default and retest.
Just curious, there are already test/jdk/sun/security/pkcs11/Secmod/cert9.db and test/jdk/sun/security/pkcs11/Secmod/key4.db, what are the reasons for updating them? Since it's binary file, I can't tell what changes they are for... |
Without updating Regarding your second question, every |
Thanks for the explanation~ |
Good point. No it does not work. The test failed to initialize the NSS module, printed "skipping", and returned pass. I converted the cert8/key3 pair to cert9/key4 and created a pkcs11.txt file. Now it works. |
Thanks, changes look good to me. |
@mcpowers 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 158 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 (@valeriepeng) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
@valeriepeng Thanks for the review! |
/integrate |
/sponsor |
Going to push as commit 6e1aacd.
Your commit was automatically rebased without conflicts. |
@valeriepeng @mcpowers Pushed as commit 6e1aacd. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
https://bugs.openjdk.org/browse/JDK-8296631
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/15644/head:pull/15644
$ git checkout pull/15644
Update a local copy of the PR:
$ git checkout pull/15644
$ git pull https://git.openjdk.org/jdk.git pull/15644/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 15644
View PR using the GUI difftool:
$ git pr show -t 15644
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/15644.diff
Webrev
Link to Webrev Comment