In my case, I have DBI::MySql, but no MySql server at all.  I've thought of filtering 
out through my PostgreSQL db, modules which match certain patterns (like MySql), 
but have not explored such possibilities yet.

In the interest of automation, I'm looking (some day) at how to connect to an 
"always there" db for the driver specified and check for the results to see if the db 
server is available.  This could then be done in Makefile.PL Maybe a new method in 
DBD (like is_db_available or something).  PostgreSQL has template1, and 
apparently MySQL has test, so that's a start for "always there" db's.

Cheers,
Rob

> On Tue, 14 May 2002, Automated Perl Test Account wrote:
> 
> > This is an error report generated automatically by CPANPLUS.
> > Below is the error stack during 'make test':
> >
> > PERL_DL_NONLAZY=1 /usr/bin/perl -Iblib/arch -Iblib/lib
> > -I/usr/lib/perl5/5.6.1/i386-linux -I/usr/lib/perl5/5.6.1 -e
> > 'use Test::Harness qw(&runtests $verbose);
> > $verbose=(eval(chr(36).q(|=1))-1); runtests @ARGV;' t/*.t
> > t/0_base..................ok
> > t/1_create................DBI->connect(test) failed: Can't
> > connect to local MySQL server through socket
> > '/var/lib/mysql/mysql.sock' (2) at t/test.lib line 11
> > Compilation failed in require at t/1_create.t line 7. dubious
> >     Test returned status 255 (wstat 65280, 0xff00)
> 
> There's been a few failed reports like this caused by apparently
> not having the database server either running or accessable when
> running the tests. If that's the case, that's not really the
> fault of the module - perhaps CPANPLUS, when running in automatic
> mode, should check first that the server is available, and if not,
> skip testing such packages?
> 
> best regards,
> randy kobes
> 
> 
> 



Reply via email to