Re: DBI svn 13624 not very healthy

H.Merijn Brand wrote:
> On Thu, 03 Dec 2009 17:35:50 +0000, Martin Evans
> <[email protected]> wrote:
> 
>> H.Merijn Brand wrote:
>>> Current checkout:
>>>
>>> commit a5a9fc491c2f0316a39af0adb5cd82b39dabafae
>>> Author: mjevans <mjevans@50811bd7-b8ce-0310-adc1-d9db26280581>
>>> Date:   Wed Dec 2 10:08:18 2009 +0000
>>>
>>>     Needs SQL types and DBIstcf_XXX
>>>
>>>
>>>     git-svn-id: http://svn.perl.org/modules/dbi/trunk@13624 50811bd7-b8ce-0310-adc1-d9db26280581
>>>
>>>
>>>
>>> t/90sql_type_cast.t ........ 1/?
>>> #   Failed test 'result, non numeric cast to double'
>>> #   at t/90sql_type_cast.t line 97.
>>> #          got: '2'
>>> #     expected: '1'
>>
>>
>>> #   Failed test 'result, non numeric cast to double (strict)'
>>> #   at t/90sql_type_cast.t line 97.
>>> #          got: '2'
>>> #     expected: '0'
>> I'd expect those 2 at the moment as there is an outstanding issue with
>> Perl_sv_2nv. I left them in so if Tim had any time he could see them.
>>
>>> #   Failed test 'result, 4 byte max unsigned int cast to int'
>>> #   at t/90sql_type_cast.t line 97.
>>> #          got: '2'
>>> #     expected: '1'
>>> # Looks like you failed 3 tests of 26.
>>> t/90sql_type_cast.t ........ Dubious, test returned 3 (wstat 768, 0x300)
>>> Failed 3/26 subtests
>> What platform did you run this test on - a 64bit platform? Can you email
>> me your Perl -V.

This latter one is fixed now. I was checking $Config{longsize} and have
changed it to $Config{ivsize}. Thanks to Tux for pointing it out and
testing the fix.

> Summary of my perl5 (revision 5 version 10 subversion 0) configuration:
<snipped>
>     intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=12345678
>     d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
>     ivtype='long long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8
>     alignbytes=4, prototype=define
<snipped>


> Most of my other platforms are 64bitall, which is why I /develop/ on
> this box.
> 
>> I don't really know how/why each test is duplicated with different
>> prefixes in those below - I don't get that.
> 

Perhaps Tim can tell me how to fix that.

Martin