Re: ANNOUNCE: DBD::Oracle 1.25 Release Candidate

On 06/09/10 15:00, H.Merijn Brand wrote:
> On Mon, 06 Sep 2010 14:52:52 +0100, "Martin J. Evans"
> <[email protected]> wrote:
> 
>> To fix the DiscardString issue above could you please change
>>
>> #if DBISTATE_VERSION > 94
>>
>> to
>>
>> #if DBIXS_REVISION >= 13590
>>
>> in oci8.c around line 3793.
> 
> Still fails with that change ...

that change is to allow DiscardString to work again not to fix segfaults in DBD::Oracle.

Perhaps I did not make that clear enough - sorry.

Martin

> Test Summary Report
> -------------------
> t/31lob.t             (Wstat: 256 Tests: 5 Failed: 0)
>   Non-zero exit status: 1
>   Parse errors: Bad plan.  You planned 12 tests but ran 5.
> t/58object.t          (Wstat: 1024 Tests: 51 Failed: 4)
>   Failed tests:  27, 31, 33-34
>   Non-zero exit status: 4
> Files=31, Tests=2126, 19 wallclock secs ( 0.34 usr  0.03 sys +  4.43 cusr  0.51 csys =  5.31 CPU)
> Result: FAIL
> Failed 2/31 test programs. 4/2126 subtests failed.
> 
> 
> DBD-Oracle-1.25-RC2 406 > prove -vbw t/31lob.t
> t/31lob.t ..
> 1..12
> ok 1 - returned valid locator
> ok 2 - inserted into BLOB successfully
> ok 3 - got back what we put in
> ok 4 - returned valid locator
> ok 5 - returned valid locator
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 7/12 subtests
> 
> Test Summary Report
> -------------------
> t/31lob.t (Wstat: 256 Tests: 5 Failed: 0)
>   Non-zero exit status: 1
>   Parse errors: Bad plan.  You planned 12 tests but ran 5.
> Files=1, Tests=5,  1 wallclock secs ( 0.03 usr  0.00 sys +  0.10 cusr  0.02 csys =  0.15 CPU)
> Result: FAIL
> 
>