On 7/31/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
*Derby* 426908/2006-07-30 19:46:17 CEST
*derbyall*
Failed Tests OK Skip Duration Platform
-------------------------------------------------------
*Jvm: 1.6*
22 728 706 0 107.99% SunOS-5.10_i86pc-i386
Details in
http://www.multinet.no/~solberg/public/Apache/DerbyJDK16Jvm1.6/Limited/testSummary-426908.html
Attempted failure analysis in
http://www.multinet.no/~solberg/public/Apache/Failures/DerbyJDK16Jvm1.6/426908.html
I saw these failure and was surprised, but it didn't seem to be
related to anything I was doing in my patch (which hasn't gone in yet,
so there's proof of sorts).
I don't understand why these diffs didn't show up on 7/19's run ( see:
http://www.multinet.no/~solberg/public/Apache/DerbyJDK16Jvm1.6/Limited/derbyall_history.html)
because the files in the harness dir have since only been changed in
what seems to me unrelated ways...
But I am wondering, if maybe one item too many slipped into Sed.java...
It seems to me that this:
searchStrings.addElement("java.sql.SQLException:");
is on purpose getting changed into this:
subStrings.addElement(SQL_EXCEPTION_FILTERED_SUBSTITUTION);
(i.e. private static final String
SQL_EXCEPTION_FILTERED_SUBSTITUTION
= "SQL Exception:";)
whereas it seems the jdk14/15 the output may be (see e.g. compressTable.sql):
ERROR 38000: The exception 'java.sql.SQLException: Schema 'GROUP' does
not exist' was thrown while evaluating an expression.
So, maybe the java.sql.SQLException should *not* get filtered?
Just some thoughts.
Myrna
