[EMAIL PROTECTED] wrote:
[Auto-generated mail]

*tinderbox_trunk16* 520689/2007-03-21 02:22:23 CET

Failed  Tests    OK  Skip  Duration       Suite
-------------------------------------------------------
*Jvm: 1.6*
  SunOS-5.10_i86pc-i386
    43    409    366     0   104.43%     derbyall
    F:26,E:101    6196    6069     0   451.94%     
org.apache.derbyTesting.functionTests.suites.All

My guess that this is my change, 520663. I ran tests on jdk 1.5 but not 1.6. I bet that under jdk1.6 Derby is already calling initCause().

Feel free to back out if that's the case, I don't have time now to investigate further.

Dan.


r520663 | djd | 2007-03-21 00:44:32 +0100 (Wed, 21 Mar 2007) | 4 lines

Set Throwable.initCause() in a couple of locations at the JDBC level where we setup nested SQLExceptions. This means that automatically the stack trace for a database failed to start includes the reason for the failure, rather than just "see next exception". This is a great help when running
JUnit tests and getting failures to start a database.

Reply via email to