db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren" <m.v.lunte...@gmail.com>
Subject Re: Regression Test Failure! - Derby 426908 - Sun DBTG
Date Mon, 31 Jul 2006 17:34:52 GMT
On 7/31/06, Ole.Solberg@sun.com <Ole.Solberg@sun.com> 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:
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:
is on purpose getting changed into this:
    (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.


View raw message