Details
-
Bug
-
Resolution: Fixed
-
P2
-
11, 12, 13
-
b16
-
b20
-
Verified
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8253491 | 11.0.10-oracle | John Jiang | P2 | Closed | Fixed | b01 |
JDK-8230896 | 11.0.6 | John Jiang | P2 | Resolved | Fixed | b01 |
JDK-8230754 | 11.0.5 | John Jiang | P2 | Resolved | Fixed | b07 |
Description
Test .dll seems need to be re-built.
(with given +x execution permission to the test .dll) There are many pkcs11 tests failed due to:
java.security.ProviderException: Initialization failed
...
Caused by: java.io.IOException: The specified module could not be found.
Attachments
Issue Links
- backported by
-
JDK-8230754 Many pkcs11 tests failed in Provider initialization, after compiler on Windows changed
- Resolved
-
JDK-8230896 Many pkcs11 tests failed in Provider initialization, after compiler on Windows changed
- Resolved
-
JDK-8253491 Many pkcs11 tests failed in Provider initialization, after compiler on Windows changed
- Closed
- relates to
-
JDK-8148501 Upgrade NSS library used in tests to the latest version
- Resolved
-
JDK-8164639 Configure PKCS11 tests to use user-supplied NSS libraries
- Resolved
-
JDK-8203795 Change default compiler on Windows to VS2017
- Closed
1.
|
Problem list pkcs11 tests on windows | Resolved | Rajan Halade |