FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

Is "make test" for DBD::Sybase expected to pass 100% nowadays?  Time was it
didn't IIRC, but it worked OK anyway.  

--jkl


> -----Original Message-----
> From: Wilson, John [mailto:John.Wilson AT Savvis.net]
> Sent: October 21, 2002 11:04 AM
> To: TDS Development Group
> Subject: [freetds] Re: Need help with DBD::Sybase 'make test' fails us
> ing FreeTDS.
> 
> 
> James/Nick:
> Ok, I grabbed the freetds-current from the webpage and 
> rebuilt it using
> ./configure --prefix=$HOME/devel/usr/local --with-tdsver=4.2
> 
> I also rebuilt DBI-1.30 to make sure it was good to go with the newer
> freetds.  That passed it's test too.
> 
> DBD::Sybase make test results:
> ______________________________________________________________
> ______________
> ____________________
> [jwilson@vntwb1da DBD-Sybase-0.94_02]$ make test
> PERL_DL_NONLAZY=1 /home/jwilson/devel/usr/local/bin/perl -Iblib/arch
> -Iblib/lib 
> -I/home/jwilson/devel/usr/local/lib/perl5/5.00503/sun4-solaris
> -I/home/jwilson/devel/usr/local/lib/perl5/5.00503 -e 'use 
> Test::Harness
> qw(&runtests $verbose); $verbose=0; runtests @ARGV;' t/*.t
> t/autocommit........ok
> t/base..............ok
> t/exec..............dubious
>         Test returned status 0 (wstat 139, 0x8b)
>         test program seems to have generated a core
> t/fail..............ct_send(ct_dynamic(CS_PREPARE)) returned 0 at
> blib/lib/DBD/Sybase.pm line 105.
> Can't call method "execute" on an undefined value at t/fail.t line 66.
> dubious
>         Test returned status 22 (wstat 5632, 0x1600)
> DIED. FAILED tests 2, 5-13
>         Failed 10/13 tests, 23.08% okay
> t/login.............ok
> t/main..............FAILED tests 13-14, 16
>         Failed 3/16 tests, 81.25% okay
> t/nsql..............ok
> t/place.............ct_send(ct_dynamic(CS_PREPARE)) returned 0 at
> blib/lib/DBD/Sybase.pm line 105.
> Can't call method "execute" on an undefined value at 
> t/place.t line 64.
> dubious
>         Test returned status 22 (wstat 5632, 0x1600)
> DIED. FAILED tests 3-11
>         Failed 9/11 tests, 18.18% okay
> t/xblob.............DBD::Sybase::db do failed: Server message 
> number=262
> severity=14 state=1 line=1 server=RTDBASESQL text=CREATE 
> TABLE permission
> denied in database 'tempdb'. at t/xblob.t line 47.
> DBD::Sybase::db do failed: Server message number=208 
> severity=16 state=1
> line=1 server=RTDBASESQL text=Invalid object name 
> 'blob_test'. at t/xblob.t
> line 55.
> DBD::Sybase::st execute failed: Server message number=208 severity=16
> state=1 line=1 server=RTDBASESQL text=Invalid object name 
> 'blob_test'. at
> t/xblob.t line 62.
> no statement executing at t/xblob.t line 63.
> Out of memory during ridiculously large request at t/xblob.t line 69.
> dubious
>         Test returned status 22 (wstat 5632, 0x1600)
> DIED. FAILED tests 3-6
>         Failed 4/6 tests, 33.33% okay
> Failed Test  Status Wstat Total Fail  Failed  List of failed
> --------------------------------------------------------------
> --------------
> ---
> t/exec.t          0   139    ??   ??       %  ??
> t/fail.t         22  5632    13   10  76.92%  2, 5-13
> t/main.t                     16    3  18.75%  13-14, 16
> t/place.t        22  5632    11    9  81.82%  3-11
> t/xblob.t        22  5632     6    4  66.67%  3-6
> Failed 5/9 test scripts, 44.44% okay. 26/62 subtests failed, 
> 58.06% okay.
> make: *** [test_dynamic] Error 2
> ______________________________________________________________
> ______________
> _____________
> 
> We'll this is much better than it was... I'm looking into these 
> failed tests... also working with our DBA to make sure permissions
> are setup correctly.
> 
> I assume some of these may just be the test need some tweeking.  
> At least there are no more relocation errors.
> 
> Note, the latest freetds was installed in my test ~/usr/local 
> file system
> and SYBASE was set to this path. LD_LIBRARY_PATH also 
> included this path, as
> well as /usr/local/lib (at the end).
> 
> Almost there... 
> regards,
> 
> jd wilson
> 
> 
> -----Original Message-----
> From: Lowden, James K [mailto:LowdenJK AT bernstein.com]
> Sent: Monday, October 21, 2002 9:32 AM
> To: TDS Development Group
> Subject: [freetds] Re: Need help with DBD::Sybase 'make test' fails us
> ing FreeTDS.
> 
> 
> > From: Castellano, Nicholas [mailto:Nicholas_Castellano AT acml.com]
> > Sent: October 21, 2002 9:24 AM
> > 
> > Actually, I added cs_ctx_global() after the last release, in 
> > response to
> > this issue.  So, the answer to this one is the increasingly 
> > popular "update
> > from CVS."
> 
> OK, but riddle me this, Batman: linking DBD::Sybase to 
> FreeTDS is not a new
> trick.  People have been doing that since Lincoln was 
> president.  Well,
> since before HP bought Compaq.  How did they do it without 
> cs_ctx_global?
> 
> > 
> > -----Original Message-----
> > From: bounce-freetds-145195 AT franklin.oit.unc.edu
> > [mailto:bounce-freetds-145195 AT franklin.oit.unc.edu] 
> > Sent: Monday, October 21, 2002 3:01 AM
> > To: TDS Development Group
> > Subject: [freetds] Re: Need help with DBD::Sybase 'make test' 
> > fails us ing
> > FreeTDS.
> > 
> > I know for certain that FreeTDS exposes the variable in question:
> > 
> > $ pwd;nm libct.so.0.0 |grep cs_ctx_global
> > /usr/local/lib
> > 00002ee0 T _cs_ctx_global
> > 
> > and that it works with DBD::Sybase (yea, even on Solaris).  
> > I'm not being
> > defensive; I just want you to know this *will* work, once 
> you get the
> > Solaris kinks out.  
> [...]
>  
> 
> ---
> You are currently subscribed to freetds as: [LowdenJK AT bernstein.com]
> To unsubscribe, forward this message to 
> $subst('Email.Unsub')
> 


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above.  If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.