I did so and now when I do an 'make test TEST_VERBOSE=1' Ill get: PERL_DL_NONLAZY=1 /usr/bin/perl -Iblib/arch -Iblib/lib -I/usr/lib/perl5/5.6.0/i386-linux -I/usr/lib/perl5/5.6.0 -e 'use Test::Harness qw(&runtests $verbose); $verbose=1; runtests @ARGV;' t/*.t t/01base............1..5 ok 1 ok 2 ok 3 ok 4 ok 5 ok t/02simple..........1..17 ok 1 Test 2: connecting to the database ok 2 Test 3: create test table
And here it just stops. Ill have to abort it with a Ctrl+C. > John, > > Would you do me a favor and go into ODBC.pm and comment out the whole "do" > routine. Let me know if that gets the tests to pass for you. It's some > relatively new code using SQLExecDirect instead of the whole prepare(), > execute cycle. Let me know if that passes all the tests for you. I'll try > to get MySQL up and running here, too. > > Thanks, > > Jeff > > > -----Original Message----- > > From: John Ericson [mailto:[EMAIL PROTECTED]]On Behalf Of John > > Ericson > > Sent: Sunday, February 17, 2002 1:23 PM > > To: [EMAIL PROTECTED] > > Subject: Re: ODBC fails on test > > > > > > It works! > > > > Ah, it was a simple problem with MySQL. It turned out it seached for > > mysql.sock in /var/lib/mysql while it exist in /tmp. Im having programs > > that seaches for this file in /tmp too so I have reconfiguring to do here. > > I fixed temporarly by doing an symlink from /var/lib/mysql. > > > > 'make test' performs better. It can contact the db but still fails with a > > couple of things. Ill guess its just some permissions thing on the mysql > > server. My test perl program work perfectly thoe, it connects through ODBC > > to mysql using a special user and I can do queries and all. > > > > Heres the outpur of 'make test': > > PERL_DL_NONLAZY=1 /usr/bin/perl -Iblib/arch -Iblib/lib > > -I/usr/lib/perl5/5.6.0/i386-linux -I/usr/lib/perl5/5.6.0 -e 'use > > Test::Harness qw(&runtests $verbose); $verbose=1; runtests @ARGV;' t/*.t > > t/01base............1..5 > > ok 1 > > ok 2 > > ok 3 > > ok 4 > > ok 5 > > ok > > t/02simple..........1..17 > > ok 1 > > Test 2: connecting to the database > > ok 2 > > Test 3: create test table > > dubious > > Test returned status 0 (wstat 15, 0xf) > > DIED. FAILED tests 3-17 > > Failed 15/17 tests, 11.76% okay > > t/03dbatt...........1..6 > > ok 1 > > ok 2 > > dubious > > Test returned status 0 (wstat 15, 0xf) > > DIED. FAILED tests 3-6 > > Failed 4/6 tests, 33.33% okay > > t/05meth............1..6 > > ok 1 > > ok 2 > > > >
