"make test" failing with DBD-Sybase 1.07{,_01} vs. DBI older than 1.34

Greg Earle <[email protected]>
Newsgroups gmane.comp.lang.perl.modules.dbi.sybase
Organization Isolar Technical Consulting
Message-ID <[email protected]>
Hi Michael,

This really belongs over on dbi-users I suppose, but I'm on
this list and not on that one.

I'm trying to create an RPM for DBD-Sybase (1.07 or 1.07_01,
doesn't matter) via "rpmbuild -ba".  I've cooked up a .spec
file (this is on Red Hat Enterprise Linux 3 with Sybase 12.5.1,
in case it matters) and the build works fine until it gets to
the very, very end:

[root@rhel3box SPECS]# rpmbuild -ba perl-DBD-Sybase.spec
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.18545
+ umask 022
+ cd /usr/src/redhat/BUILD

[...]

t/xblk..........ok
t/xblob.........ok 10/11# Looks like you planned 11 tests but only ran 10.
t/xblob.........dubious
         Test returned status 1 (wstat 256, 0x100)
DIED. FAILED test 11
         Failed 1/11 tests, 90.91% okay (less 3 skipped tests: 7 okay, 63.64%)
Failed Test Stat Wstat Total Fail  Failed  List of Failed
-------------------------------------------------------------------------------
t/xblob.t      1   256    11    1   9.09%  11

Why does it think 11 tests are being run, but only runs 10?

If I run t/xblob.t manually:

[root@miplws1 DBD-Sybase-1.07]# perl t/xblob.t
1..11
ok 1 - use DBI;
ok 2 - use DBD::Sybase;
ok 3 - Connect
ok 4 - Create table
ok 5 - Insert image
ok 6 - Images are the same
ok 7 - Drop table
ok 8 # skip Requires DBI 1.34
ok 9 # skip Requires DBI 1.34
ok 10 # skip Requires DBI 1.34
# Looks like you planned 11 tests but only ran 10.

This machine I'm building DBD-Sybase on has DBI-1.32 on it, not 1.34.
(That's the latest version that Red Hat Network has installed on our
Enterprise 3 machines, the one to deal with CAN-2005-0077.)

Looking closer, the last set of "ok"s I see in the file are

ok($rc, 'Drop table');
     ok($rc, 'Creat table');
     ok($rc, 'Insert image');
     ok($heximg eq $heximg2, 'Images are the same');
     ok($rc, 'Drop table');

In other words, I see 4 "ok"s inside the "SKIP: { }" section,
but it only shows up as 3 skipped tests (8, 9 and 10) in
the run - why does the test think there's only 3 inside?

Thanks,

	- Greg
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.