You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2007/08/18 00:38:35 UTC
[jira] Closed: (DERBY-1509) blobclob4BLOB expected test ouput
prints "FAIL -- unexpected exception" for exceptions that are expected
[ https://issues.apache.org/jira/browse/DERBY-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden closed DERBY-1509.
---------------------------------
> blobclob4BLOB expected test ouput prints "FAIL -- unexpected exception" for exceptions that are expected
> ---------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1509
> URL: https://issues.apache.org/jira/browse/DERBY-1509
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.1.3.2
> Reporter: Kathey Marsden
> Priority: Minor
> Fix For: 10.3.1.4, 10.4.0.0
>
>
> The test jdbcapi/blobclob4BLOB.java has a checked in master which shows test cases failing. As Rajesh pointed out in DERBY-1453, some of these exceptions are expected. This can be very confusing when diagnosing issues with this test. It would be much better if the test printed PASSED: Expected excepition instead of FAILED: *** unexpected exception**** for expected exceptions. Here is one example that Rajesh analyzed and found really should be a pass case.
> START: clobTest92
> FAIL -- unexpected exception ****************
> SQLSTATE(40XL1): A lock could not be obtained within the time requested
> There are others that need to be checked to see if they too are just a problem with the test or an actual product issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.