db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Øystein Grøvlen (JIRA) <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1844) jdbcapi/blobclob4BLOB.java fails with JCC drivers
Date Mon, 18 Sep 2006 12:49:23 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1844?page=comments#action_12435470 ] 
            
Øystein Grøvlen commented on DERBY-1844:
----------------------------------------

The exception messages was introduced by DERBY-1516, for which the patch contains several
of the:

-Known JCC Bug 5914
+FAIL: Caught exception java.lang.NegativeArraySizeException

I agree with John that we should avoid FAIL-messages in the master file.  I think for most
tests, FAIL means that the test fails, not an expected failure of a test case.  In this test,
such messages are also expected for the embedded framework, but in that case the name of the
exception is replaced by asterisks:

FAIL -- unexpected exception ****************

I have not found out how this is achieved, but maybe this is an alternative to separate canons?

> jdbcapi/blobclob4BLOB.java fails with JCC drivers
> -------------------------------------------------
>
>                 Key: DERBY-1844
>                 URL: http://issues.apache.org/jira/browse/DERBY-1844
>             Project: Derby
>          Issue Type: Test
>          Components: Regression Test Failure
>    Affects Versions: 10.3.0.0
>         Environment: IBM JDK 1.4.2
>            Reporter: Deepa Remesh
>
> Test fails with JCC versions 2.4, 2.6 and 2.8. 
> Sample diff:
> < FAIL: Caught exception java.lang.NegativeArraySizeException
> 592a592
> > FAIL: Caught exception java.lang.NegativeArraySizeException: 

-- 
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