[ http://issues.apache.org/jira/browse/DERBY-788?page=all ]
Kristian Waagan updated DERBY-788:
--
Attachment: DERBY-788-1a.diff
DERBY-788-1a.stat
'DERBY-788-1a.diff' is a patch that replaces the 16 byte key with a 8 byte key
for the DES
[ http://issues.apache.org/jira/browse/DERBY-788?page=all ]
Kristian Waagan updated DERBY-788:
--
Other Info: [Patch available]
'store/encryptionKey.sql' fails on Solaris 10
-
Key: DERBY-788
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
On 2/9/06, Mike Matrigali [EMAIL PROTECTED] wrote:
It would seem reasonable to mark this test to not run in nightlyunder solaris 10 until you resolve the jvm issue or change the test.
Maybe someone can give some hints if this is possible under thecurrent test harness (I know it is pretty easy to
Myrna van Lunteren wrote:
On 2/9/06, *Mike Matrigali* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
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
Kristian Waagan wrote:
Actually, the test won't be able to create the encrypted database,
which is the initial step for almost all test cases exercised by the
ij script.
An alternative solution would be to reduce the key length, as I have
described in the Jira issue. Since there are no
On Feb 9, 2006, at 4:15 PM, Myrna van Lunteren wrote:
There is no platform-specific skipping, or diffing. (in the test
harness)
I just want to say that the lack of diffing is somewhat by design.
Almost always, a difference in behavior on one platform (out of at
least 5 that are tested
