On Sun, May 06, 2007 at 06:13:51PM +0100, [EMAIL PROTECTED] wrote:
> t/zvp_01basics............
> # Failed test '... should be -1263462440'
> # at ./t/01basics.t line 234.
> # got: -1255073832
> # expected: -1263462440
>
> # Failed test '... should be -1263462437'
> # at ./t/01basics.t line 235.
> # got: -1255073829
> # expected: -1263462437
Interesting...
SKIP: {
skip("Math::BigInt < 1.56",2)
if $DBI::PurePerl && !eval { require Math::BigInt; require_version
Math::BigInt 1.56 };
cmp_ok(DBI::hash("foo1",1), '==', -1263462440, '... should be -1263462440');
cmp_ok(DBI::hash("foo2",1), '==', -1263462437, '... should be -1263462437');
}
Looks to me like the gofer subprocess picked up a different
Math::BigInt than the one in the parent process.
And that's probably because it used a different perl executable.
Could you do some checking along those lines?
Thanks!
I should probably just skip those tests if $^X doesn't match the path
of the 'perl' executable we find from the PATH.
Tim.
