db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Van Couvering (JIRA)" <derby-...@db.apache.org>
Subject [jira] Resolved: (DERBY-1616) Lots of jdk1.6 regression test failures with diffs because of SQL Exception instead of java.sql.SQLException
Date Wed, 02 Aug 2006 16:30:18 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1616?page=all ]

David Van Couvering resolved DERBY-1616.
----------------------------------------

    Resolution: Fixed

Sending        java/testing/org/apache/derbyTesting/functionTests/harness/Sed.java
Sending        java/testing/org/apache/derbyTesting/functionTests/master/DerbyNetClient/jdk16/ieptests.out
Sending        java/testing/org/apache/derbyTesting/functionTests/master/DerbyNetClient/jdk16/importExport.out
Sending        java/testing/org/apache/derbyTesting/functionTests/master/DerbyNetClient/jdk16/procedure.out
Sending        java/testing/org/apache/derbyTesting/functionTests/master/jdk16/closed.out
Sending        java/testing/org/apache/derbyTesting/functionTests/master/jdk16/releaseCompileLocks.out
Transmitting file data ......
Committed revision 428044.


> Lots of jdk1.6 regression test failures with diffs because of  SQL Exception instead
of java.sql.SQLException
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1616
>                 URL: http://issues.apache.org/jira/browse/DERBY-1616
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.2.0.0
>         Environment: jdk16 /windows.
>            Reporter: Sunitha Kambhampati
>         Assigned To: David Van Couvering
>             Fix For: 10.2.0.0
>
>         Attachments: DERBY-1616.diff, derbyall_report.txt
>
>
> jdk16 derbyall derbyall: 19 failures
>     derbyall/derbyall.fail:lang/compressTable.sql
>     derbyall/derbyall.fail:lang/nestedCommit.sql
>     derbyall/derbyall.fail:lang/outparams.java
>     derbyall/derbyall.fail:lang/procedure.java
>     derbyall/derbyall.fail:lang/procedureInTrigger.sql
>     derbyall/derbyall.fail:tools/importExportThruIJ.sql
>     derbyall/derbyall.fail:tools/ieptests.sql
>     derbyall/derbyall.fail:tools/iepnegativetests.sql
>     derbyall/derbyall.fail:jdbcapi/statementJdbc20.java
>     derbyall/derbyall.fail:jdbcapi/statementJdbc30.java
>     derbyall/derbyall.fail:jdbcapi/parameterMapping.java
>     derbyall/derbyall.fail:i18n/iepnegativetests_ES.sql
>     derbyall/derbynetclientmats/derbynetclientmats.fail:jdbc4/ClosedObjectTest.junit
>     derbyall/derbynetclientmats/derbynetclientmats.fail:jdbc4/UnsupportedVetter.junit
>     derbyall/derbynetclientmats/derbynetclientmats.fail:jdbc4/VerifySignatures.junit
>     derbyall/encryptionAll/encryption.fail:stress/stress.multi
>     derbyall/encryptionAll/storemats.fail:store/streamingColumn.java
>     derbyall/storeall/storeall.fail:store/TransactionTable.sql
>     derbyall/storeall/storemats.fail:store/streamingColumn.java

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message