AW: DBD::Informix Make test Problem

AW: DBD::Informix Make test Problem

am 16.02.2007 09:13:30 von Govinda.Pfister

------_=_NextPart_001_01C751A2.5759E25B
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello Jonathan,
=20
I just ran your proposed test and it brought some interesting debugging =
results. I think the problem is with the date columns that are created. =
The expected results differ from the real results. Though I do not know =
at the moment how we can fix that...
=20
Govinda
=20
sh ./test.one.sh t/t4[13]* t/t65*
----------------
# DBI->connect('dbi:Informix:arsystem_63@arsds680', 'aradmin', =
'XXXXXXXX');
# Connect Attribute: AutoCommit =3D> 1
# Connect Attribute: ChopBlanks =3D> 1
# Connect Attribute: PrintError =3D> 1
1..19
ok 1
# This is a regular logged database
# AutoCommit mode is 1
# InTransaction =3D 0
# InTransaction =3D 0
# Set AutoCommit Off - start manual transactions
# AutoCommit mode is now 0
# InTransaction =3D 1
# InTransaction =3D 1
# Test: do('
# CREATE TEMP TABLE DBD_IX_Trans01
# (
# Col01 SERIAL NOT NULL PRIMARY KEY,
# Col02 CHAR(20) NOT NULL,
# Col03 DATE NOT NULL,
# Col04 DATETIME YEAR TO FRACTION(5) NOT NULL
# )
# '):
ok 2
# InTransaction =3D 1
ok 3
# InTransaction =3D 1
# Test: do('INSERT INTO DBD_IX_Trans01 VALUES(0, 'Elfdom', '12/25/96', =
'2004-02-29 23:59:54.32109')'):
ok 4
# InTransaction =3D 1
# InTransaction =3D 1
ok 5
ok 6
# Warning Message:
# <>
# SQLSTATE =3D
# InTransaction =3D 1
# Test: do('INSERT INTO DBD_IX_Trans01 VALUES(0, 'Elfdom', '12/25/96', =
'2004-02-29 23:59:54.32109')'):
ok 7
# Test: do('INSERT INTO DBD_IX_Trans01 VALUES(0, 'Santa Claus Home', =
'12/25/96', '2004-02-29 23:59:54.32109')'):
ok 8
ok 9
# Row 1: Got unexpected value <<12/25/2096>> for col03 (key value =3D 2) =
when <<12/25/1996>> expected!
# Row 2: Got unexpected value <<12/25/2096>> for col03 (key value =3D 3) =
when <<12/25/1996>> expected!
# FAILED: 0 rows were correct; 2 rows had faulty data
not ok 10
# InTransaction =3D 1
ok 11
# Warning Message:
# <>
# SQLSTATE =3D
# Test: do('INSERT INTO DBD_IX_Trans01 VALUES(0, 'Santa Claus Home', =
'12/25/96', '2004-02-29 23:59:54.32109')'):
ok 12
# Test: do('INSERT INTO DBD_IX_Trans01 VALUES(0, 'Elfdom', '12/25/96', =
'2004-02-29 23:59:54.32109')'):
ok 13
# Row 1: Got unexpected value <<12/25/2096>> for col03 (key value =3D 4) =
when <<12/25/1996>> expected!
# Row 2: Got unexpected value <<12/25/2096>> for col03 (key value =3D 5) =
when <<12/25/1996>> expected!
# FAILED: 0 rows were correct; 2 rows had faulty data
not ok 14
# InTransaction =3D 1
# Row 1: Got unexpected value <<12/25/2096>> for col03 (key value =3D 4) =
when <<12/25/1996>> expected!
# Row 2: Got unexpected value <<12/25/2096>> for col03 (key value =3D 5) =
when <<12/25/1996>> expected!
# FAILED: 0 rows were correct; 2 rows had faulty data
not ok 15
# Test: do('DELETE FROM DBD_IX_Trans01'):
ok 16
ok 17
# Warning Message:
# <>
# SQLSTATE =3D
# InTransaction =3D 1
# Row 1: Got unexpected value <<12/25/2096>> for col03 (key value =3D 4) =
when <<12/25/1996>> expected!
# Row 2: Got unexpected value <<12/25/2096>> for col03 (key value =3D 5) =
when <<12/25/1996>> expected!
# FAILED: 0 rows were correct; 2 rows had faulty data
not ok 18
ok 19
# *** Testing of DBD::Informix complete ***
# *** There appear to be some problems! ***
# DBI->connect('dbi:Informix:arsystem_63@arsds680', 'aradmin', =
'XXXXXXXX');
# Connect Attribute: ChopBlanks =3D> 1
1..20
ok 1
# This is a regular logged database
# Default AutoCommit is On
# AutoCommit was set to Off
# Test: do('
# CREATE TEMP TABLE DBD_IX_Trans01
# (
# Col01 SERIAL NOT NULL PRIMARY KEY,
# Col02 CHAR(20) NOT NULL,
# Col03 DATE NOT NULL,
# Col04 DATETIME YEAR TO FRACTION(5) NOT NULL
# )
# '):
ok 2
ok 3
ok 4
# Test: do('INSERT INTO DBD_IX_Trans01 VALUES(0, 'Elfdom', '12/25/96', =
'2004-02-29 23:59:54.32109')'):
ok 5
# Row 1: Got unexpected value <<12/25/2096>> for col03 (key value =3D 1) =
when <<12/25/1996>> expected!
# FAILED: 0 rows were correct; 1 rows had faulty data
not ok 6
ok 7
ok 8
# Warning Message:
# <>
# SQLSTATE =3D
# Test: do('INSERT INTO DBD_IX_Trans01 VALUES(0, 'Elfdom', '12/25/96', =
'2004-02-29 23:59:54.32109')'):
ok 9
# Test: do('INSERT INTO DBD_IX_Trans01 VALUES(0, 'Santa Claus Home', =
'12/25/96', '2004-02-29 23:59:54.32109')'):
ok 10
# Row 1: Got unexpected value <<12/25/2096>> for col03 (key value =3D 2) =
when <<12/25/1996>> expected!
# Row 2: Got unexpected value <<12/25/2096>> for col03 (key value =3D 3) =
when <<12/25/1996>> expected!
# FAILED: 0 rows were correct; 2 rows had faulty data
not ok 11
ok 12
# Warning Message:
# <>
# SQLSTATE =3D
# Test: do('INSERT INTO DBD_IX_Trans01 VALUES(0, 'Santa Claus Home', =
'12/25/96', '2004-02-29 23:59:54.32109')'):
ok 13
# Test: do('INSERT INTO DBD_IX_Trans01 VALUES(0, 'Elfdom', '12/25/96', =
'2004-02-29 23:59:54.32109')'):
ok 14
# Row 1: Got unexpected value <<12/25/2096>> for col03 (key value =3D 4) =
when <<12/25/1996>> expected!
# Row 2: Got unexpected value <<12/25/2096>> for col03 (key value =3D 5) =
when <<12/25/1996>> expected!
# FAILED: 0 rows were correct; 2 rows had faulty data
not ok 15
# Row 1: Got unexpected value <<12/25/2096>> for col03 (key value =3D 4) =
when <<12/25/1996>> expected!
# Row 2: Got unexpected value <<12/25/2096>> for col03 (key value =3D 5) =
when <<12/25/1996>> expected!
# FAILED: 0 rows were correct; 2 rows had faulty data
not ok 16
# Test: do('DELETE FROM DBD_IX_Trans01'):
ok 17
ok 18
# Warning Message:
# <>
# SQLSTATE =3D
# Row 1: Got unexpected value <<12/25/2096>> for col03 (key value =3D 4) =
when <<12/25/1996>> expected!
# Row 2: Got unexpected value <<12/25/2096>> for col03 (key value =3D 5) =
when <<12/25/1996>> expected!
# FAILED: 0 rows were correct; 2 rows had faulty data
not ok 19
ok 20
# *** Testing of DBD::Informix complete ***
# *** There appear to be some problems! ***
# DBI->connect('dbi:Informix:arsystem_63@arsds680', 'aradmin', =
'XXXXXXXX');
# Connect Attribute: ChopBlanks =3D> 1
1..16
ok 1
# Test: do('
# CREATE TEMP TABLE DBD_IX_TestTable
# (
# Col01 SERIAL NOT NULL PRIMARY KEY,
# Col02 CHAR(30) NOT NULL,
# Col03 DATE NOT NULL,
# Col04 DATETIME YEAR TO FRACTION(5) NOT NULL
# )
# '):
ok 2
ok 3
# Test: do('INSERT INTO DBD_IX_TestTable VALUES(0, 'Mornington =
Crescent', '12/08/40', '1940-12-08 06:45:32.54321')'):
ok 4
# Test: do('INSERT INTO DBD_IX_TestTable VALUES(0, 'King''s Cross / St =
Pancras', '12/08/40', '1940-12-08 06:45:32.54321')'):
ok 5
ok 6
# Row 1: Got unexpected value <<12/08/2040>> for col03 (key value =3D 1) =
when <<12/08/1940>> expected!
# Row 2: Got unexpected value <<12/08/2040>> for col03 (key value =3D 2) =
when <<12/08/1940>> expected!
# FAILED: 0 rows were correct; 2 rows had faulty data
not ok 7
ok 8
# Cursor name 0: c_000000005 OK
# Cursor name 1: c_000000005 OK
# Cursor name 2: c_000000005 OK
# UPDATE DBD_IX_TestTable SET Col02 =3D ? WHERE CURRENT OF c_000000005
ok 9
# DELETE FROM DBD_IX_TestTable WHERE CURRENT OF c_000000005
ok 10
ok 11
ok 12
Row 1: Field 0: <<1>>
Row 1: Field 1: <>
Row 1: Field 2: <<12/08/2040>>
Row 1: Field 3: <<1940-12-08 06:45:32.54321>>
ok 13
Row 2: Field 0: <<2>>
Row 2: Field 1: <>
Row 2: Field 2: <<12/08/2040>>
Row 2: Field 3: <<1940-12-08 06:45:32.54321>>
ok 14
# Row 1: Got unexpected value <<12/08/2040>> for col03 (key value =3D 1) =
when <<12/08/1940>> expected!
# FAILED: 0 rows were correct; 1 rows had faulty data
not ok 15
ok 16
# *** Testing of DBD::Informix complete ***
# *** There appear to be some problems! ***

----------------

________________________________

Von: Jonathan Leffler [mailto:jonathan.leffler@gmail.com]=20
Gesendet: Donnerstag, 15. Februar 2007 15:09
An: Pfister, Govinda
Betreff: Fwd: DBD::Informix Make test Problem



On 2/15/07, Govinda.Pfister@telekom.de =
wrote:=20

Hi Jonathan,
=20
I can=B4t see any new replies from you in this mail. Do I miss =
anything?
=20
Govinda
=20
PS: In my last mail to you I added:




Sorry, Govinda, I don't know what happened. Gmail reckons I sent the =
email response below; if it didn't arrive, I'm sorry.

Where I said 'use test.verbose.sh', I mis-spoke and should have said =
'use test.one.sh'. Basically, I want to see which test is failing, and =
what the nature of the failure is. My comment about "needing several =
iterations" is noting that we may end up needing to run the tests with =
DBI_TRACE set higher to find out where the trouble is - though I hope to =
avoid that.=20

I am quite puzzled - normally, most of the DBD::Informix tests bail out =
the moment the first test fails, rather than continuing (it can be hard =
to determine a valid state for the database if something fails). =
However, it is a number of years since I looked at these tests in any =
detail.=20

Please let me know when you receive this - if you don't respond fairly =
promptly, I'll resend to dbi-users and hope you receive it that way (but =
then, please look to see whether my emails are being filtered into =
spam).=20

---------- Forwarded message ----------
From: Jonathan Leffler
Date: Feb 14, 2007 10:24 AM=20
Subject: Re: DBD::Informix Make test Problem
To: "Govinda.Pfister@telekom.de"




On 2/14/07, Govinda.Pfister@telekom.de =
wrote:=20

Hello Jonathan,
=09
Here comes the output of esql -V=20
=09
=09
IBM Informix CSDK Version 2.90, IBM Informix-ESQL Version 2.90.UC4
Software Serial Number AAA#B000000


A 32-bit CSDK, as I expected. OK.=20




And I do only have the following sh-scripts in my DBD::Informix =
Install:
=09
root@ds68001a:/.cpan/build/DBD-Informix-2005.02 # ls *.sh
test.all.sh test.c4gl.sh test.one.sh test.quiet.sh =
test.run.sh



Sorry - use test.one.sh (which will test several)..=20

I may well need to go through several iterations getting more =
information as we go.





-----Ursprüngliche Nachricht-----
Von: Jonathan Leffler [mailto:jonathan.leffler@gmail.com]
Gesendet: Mittwoch, 14. Februar 2007 18:25=20
An: Pfister, Govinda
Cc: dbi-users@perl.org; Janssen, Johann
Betreff: Re: DBD::Informix Make test Problem
=09
On 2/14/07, Govinda.Pfister@telekom.de < Govinda.Pfister@telekom.de =
> wrote:
=09
> I do have a problem with "make test" run for the DBD::Informix =
module.
> The error is shown below. What is the problem? Is it safe to proceed
> to "make install"?=20
>
=09
Not comfortable - I wouldn't recommend the install.
=09
uname -a
> ------------------------------
> SunOS ds68001a 5.10 Generic_118833-18 sun4u sparc SUNW,Sun-Fire-V490
>
>
> env | sort
> ---------------------------
> CMASK=3D022
> DBD_INFORMIX_DATABASE=3Darsystem_63@arsds680
> DBD_INFORMIX_NO_SBSPACE=3D1
> DBD_INFORMIX_PASSWORD=3DXXXXXXX
> DBD_INFORMIX_USERNAME=3DXXXXXXX=20
> [...]
> _=3D/bin/env
>
>
>
> dbaccess -V
> ----------------------------
> DB-Access Version 9.40.FC6
> Software Serial Number AAA#B000000
=09
=09
64-bit database server...=20
=09
esql -v
> ------------
=09
=09
Next time, please use '-V' (capital letter, not lower case).
=09
[Actually, please include the output of 'esql -V' if you respond.]
=09
=09
Reading specs from /usr/local/lib/gcc/sparc- =
sun-solaris2.10/3.4.6/specs
> Configured with: ../configure --with-as=3D/usr/ccs/bin/as
> --with-ld=3D/usr/ccs/bin/ld --enable-shared =
--enable-languages=3Dc,c++,f77
> Thread model: posix gcc version 3.4.6 [...]=20
> root@ds68001a:/.cpan/build/DBD-Informix-2005.02 # esql -v Reading
> specs from /usr/local/lib/gcc/sparc-sun-solaris2.10/3.4.6/specs
> [...]
>
> perl -V
> --------------
> Summary of my perl5 (revision 5 version 8 subversion 7) =
configuration:=20
> Platform:
> osname=3Dsolaris, osvers=3D2.10, archname=3Dsun4-solaris
> uname=3D'sunos ds68001a 5.10 generic_118833-18 sun4u sparc
> sunw,sun-fire-v490 '
> config_args=3D'-ds -e -Dprefix=3D/usr/local'=20
> hint=3Drecommended, useposix=3Dtrue, d_sigaction=3Ddefine
> usethreads=3Dundef use5005threads=3Dundef useithreads=3Dundef
> usemultiplicity=3Dundef
> useperlio=3Ddefine d_sfio=3Dundef uselargefiles=3Ddefine =
usesocks=3Dundef=20
> use64bitint=3Dundef use64bitall=3Dundef uselongdouble=3Dundef
> usemymalloc=3Dn, bincompat5005=3Dundef
> Compiler:
> cc=3D'gcc', ccflags =3D'-fno-strict-aliasing -pipe
> -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64',=20
> optimize=3D'-O',
> cppflags=3D'-fno-strict-aliasing -pipe -I/usr/local/include'
> ccversion=3D'', gccversion=3D'3.4.6', =
gccosandvers=3D'solaris2.10'
> intsize=3D4, longsize=3D4, ptrsize=3D4, doublesize=3D8, =
byteorder=3D4321=20
> d_longlong=3Ddefine, longlongsize=3D8, d_longdbl=3Ddefine, =
longdblsize=3D16
> ivtype=3D'long', ivsize=3D4, nvtype=3D'double', nvsize=3D8, =
Off_t=3D'off_t',
=09
=09
=09
32-bit Perl...
=09
You must be using a CSDK 2.xx.UCx version, I think?
=09
=09
lseeksize=3D8
> alignbytes=3D8, prototype=3Ddefine
> Linker and Libraries:
> ld=3D'gcc', ldflags =3D' -L/usr/local/lib '
> libpth=3D/usr/local/lib /usr/lib /usr/ccs/lib
> libs=3D-lsocket -lnsl -lgdbm -ldl -lm -lc
> perllibs=3D-lsocket -lnsl -ldl -lm -lc
> libc=3D/lib/libc.so, so=3Dso, useshrplib=3Dfalse, =
libperl=3Dlibperl.a=20
> gnulibc_version=3D''
> Dynamic Linking:
> dlsrc=3Ddl_dlopen.xs, dlext=3Dso, d_dlsymun=3Dundef, =
ccdlflags=3D' '
> cccdlflags=3D'-fPIC', lddlflags=3D'-G -L/usr/local/lib'=20
>
>
> Characteristics of this binary (from libperl):
> Compile-time options: USE_LARGE_FILES
> Built under solaris
> Compiled at Jan 26 2007 14:13:46
> @INC:
> /usr/local/lib/perl5/5.8.7/sun4-solaris=20
> /usr/local/lib/perl5/5.8.7
> /usr/local/lib/perl5/site_perl/5.8.7/sun4-solaris
> /usr/local/lib/perl5/site_perl/5.8.7
> /usr/local/lib/perl5/site_perl
>
>
> make test=20
> ---------------
>
> PERL_DL_NONLAZY=3D1 /bin/perl5.8.7 "-MExtUtils::Command::MM" "-e"
> "test_harness(0, 'blib/lib', 'blib/arch')" t/t00basic.t t/t01stproc.t =

> t/t02ixtype.t t/t05dbase.t t/t07dblist.t t/t08fork.t t/t09exec.t
> t/t10sqlca.t t/t12bindval.t t/t13bindref.t t/t14bindcol.t
> t/t15bindtyp.t t/t20error.t t/t21mconn.t t/t22mconn.t t/t23mconn.t
> t/t24mcurs.t t/t25dratt.t t/t28dtlit.t t/t29update.t t/t30update.t=20
> t/t31nulls.t t/t32nulls.t t/t33holdcurs.t t/t35cursor.t t/t40rows.t
> t/t41txacoff.t t/t42txacon.t t/t43trans.t t/t44txansi.t t/t46chpblk.t
> t/t50update.t t/t51getinfo.t t/t53types.t t/t54native.t t/t55mdata.t=20
> t/t56tabinfo.t t/t57tables.t t/t58typeinfoall.t t/t60unlog.t
> t/t65updcur.t t/t66insert.t t/t72blob.t t/t73blobupd.t t/t74blob.t
> t/t75blob.t t/t76blob.t t/t90ius.t t/t91udts.t t/t92rows.t
> t/t93lvarchar.t t/t94bool.t t/t95int8.t t/t98pod.t t/t99clean.t=20
> t/t00basic..........ok t/t01stproc.........ok t/t02ixtype.........ok
> t/t05dbase..........ok t/t07dblist.........ok t/t08fork...........ok
> t/t09exec...........ok t/t10sqlca..........ok t/t12bindval........ok=20
> t/t13bindref........skipped
> all skipped: bind_param_inout not supported by DBD::Informix
> t/t14bindcol........ok t/t15bindtyp........ok t/t20error..........ok
> t/t21mconn..........ok t/t22mconn..........ok t/t23mconn..........ok=20
> t/t24mcurs..........ok t/t25dratt..........ok t/t28dtlit..........ok
> t/t29update.........ok t/t30update.........ok t/t31nulls..........ok
> t/t32nulls..........ok t/t33holdcurs.......ok t/t35cursor.........ok=20
> t/t40rows...........ok t/t41txacoff........dubious
> Test returned status 1 (wstat 256, 0x100) DIED. FAILED tests
> 10, 14-15, 18
> Failed 4/19 tests, 78.95% okay t/t42txacon.........ok=20
=09
=09
=09
txacoff - Transactions with autocommit off.
txacon - Transactions with autocommit on.
=09
I don't recall failures in txacoff - I would expect it pass. Please =
send the verbose output of the test.=20
=09
=09
t/t43trans..........dubious
> Test returned status 1 (wstat 256, 0x100) DIED. FAILED tests
> 6, 11, 15-16, 19
> Failed 5/20 tests, 75.00% okay
=09
=09
=09
Another set of transaction tests - please send the verbose output of =
the test.=20
=09
t/t44txansi.........skipped
> all skipped: MODE ANSI test - database 'arsystem_63@arsds680'
> is not MODE ANSI t/t46chpblk.........ok t/t50update.........skipped
> all skipped: MODE ANSI test - database ' =
arsystem_63@arsds680'
> is not MODE ANSI t/t51getinfo........ok t/t53types..........ok
> t/t54native.........ok t/t55mdata..........ok t/t56tabinfo........ok
> t/t57tables.........ok t/t58typeinfoall....ok t/t60unlog..........ok=20
> t/t65updcur.........dubious
> Test returned status 1 (wstat 256, 0x100) DIED. FAILED tests
> 7, 15
> Failed 2/16 tests, 87.50% okay
=09
=09
=09
updcur - Update with the WHERE CURRENT OF clause - again, please send =
verbose test output.=20
=09
t/t66insert.........ok
> t/t72blob...........ok
> t/t73blobupd........ok
> t/t74blob...........ok
> t/t75blob...........ok
> t/t76blob...........ok
> t/t90ius............ok
> t/t91udts...........ok=20
> t/t92rows...........ok
> t/t93lvarchar.......ok
> t/t94bool...........ok
> t/t95int8...........ok
> t/t98pod............ok
> t/t99clean..........ok
> Failed Test Stat Wstat Total Fail List of Failed=20
> =
------------------------------------------------------------ ----------
> --
> -------
> t/t41txacoff.t 1 256 19 4 10 14-15 18
> t/t43trans.t 1 256 20 5 6 11 15-16 19=20
> t/t65updcur.t 1 256 16 2 7 15
> 3 tests skipped.
> Failed 3/55 test scripts. 11/834 subtests failed.
> Files=3D55, Tests=3D834, 17 wallclock secs ( 9.53 cusr + 0.71 csys =
=3D
> 10.24=20
> CPU)
> Failed 3/55 test programs. 11/834 subtests failed.
> *** Error code 29
> make: Fatal error: Command failed for target `test_dynamic'
>
=09
To get verbose test output of the three tests:=20
=09
sh test.verbose.sh t/t4[13]* t/t65*
=09
--
Jonathan Leffler < jonathan.leffler@gmail.com =
> #include Guardian =
of DBD::Informix - v2005.02 - http://dbi.perl.org "I don't suffer from =
insanity - I enjoy every minute of it."
=09




--=20

Jonathan Leffler < jonathan.leffler@gmail.com =
> #include
Guardian of DBD::Informix - v2005.02 - http://dbi.perl.org=20
"I don't suffer from insanity - I enjoy every minute of it."=20


--=20
Jonathan Leffler #include
Guardian of DBD::Informix - v2005.02 - http://dbi.perl.org
"I don't suffer from insanity - I enjoy every minute of it."=20

------_=_NextPart_001_01C751A2.5759E25B--