It would seem reasonable to mark this test to not run in nightly under solaris 10 until you resolve the jvm issue or change the test. Maybe someone can give some hints if this is possible under the current test harness (I know it is pretty easy to mark not run under a specific JVM, just not sure of OS).
Kristian Waagan (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-788?page=all ] Kristian Waagan updated DERBY-788: ---------------------------------- Component: Regression Test Failure Added component 'Regression Test Failure', as this test fails on Solaris10 with the 'SunPCKS11-Solaris' Java Security provider (which is the default provider). Will fail until the test is changed or the provider is changed/fixed. See earlier comment for more details.'store/encryptionKey.sql' fails on Solaris 10 --------------------------------------------- Key: DERBY-788 URL: http://issues.apache.org/jira/browse/DERBY-788 Project: Derby Type: Bug Components: Services, Test, Regression Test Failure Versions: 10.0.2.1, 10.1.1.2, 10.1.2.1 Environment: Solaris 10 (generic hardware) Sun JDK 5.0 with the 'SunPCKS11-Solaris' Java Security provider Reporter: Kristian Waagan Assignee: Kristian Waagan Priority: Minor Fix For: 10.2.0.0The 'store/encryptionKey.sql' test fails on Solaris 10. Investigation revealed that the failure is caused by a difference in behavior between the 'SunPCKS11-Solaris' provider and other providers (tested with 'SunJCE' and 'IBMJCE'). The initialization of the DES cipher fails because the 16 byte key (specified in the test) is not translated to a 8 byte DES key by SecretKeyFactory.translateKey(). This might be a bug in the provider (I don't know the spec). Enquiries are being made. The exception is being thrown from the constructor of 'impl.services.jce.JCECipherProvider'.
