The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed. Resolved: Release in which this issue/RFE has been resolved. Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
The last failure is caused by
java.security.ProviderException: Initialization failed
at sun.security.pkcs11.P11Signature.initialize(P11Signature.java:311)
at sun.security.pkcs11.P11Signature.engineInitSign(P11Signature.java:392)
at java.security.Signature$Delegate.engineInitSign(Signature.java:1127)
at java.security.Signature.initSign(Signature.java:511)
at TestECDSA.testSigning(TestECDSA.java:179)
at TestECDSA.test(TestECDSA.java:167)
at TestECDSA.main(TestECDSA.java:135)
I'm still seeing this test failing frequently in jdk7.
It seems to be enough to remove an odd initialization: s.initSign(privateKey);
13-03-2015
This was addressed in jdk8 by JDK-8020424
06-11-2013
For now the test continues to failed and it failed again on 7/23/13 for JDK 8. See above or attached jtr report.
24-07-2013
For now the test continues to failed and it failed again on 7/19/13 for JDK 8. See attached report for jtr log.
19-07-2013
This is incorrectly labeled as a backport. 7193792 addresses a problem with CKR_OPERATION_ACTIVE. This is CKR_DOMAIN_PARAMS_INVALID. This bug is a result of the test machine having a version of NSS that does not support "ECC Extended". This is the same problem seen in 7193793.