Re: Test t/85gofer.t fails on m68k
- From: ch@xxxxxxxxxx (Christian Hammers)
- Date: Tue, 28 Aug 2007 00:13:11 +0200
Hello
On 2007-08-20 Tim Bunce wrote:
On Sun, Aug 19, 2007 at 07:35:28PM +0200, Christian Hammers wrote:
Hello
The Debian autobuilders for arm and m68k fail while trying test
t/85gofer.t with the following messages:
t/zvxgp_85gofer...........
# Failed test 'pipeone: DBI
connect('transport=null;policy=pedantic;dsn=dbi:Gofer:transport=pipeone;policy=pedantic;perl=/usr/bin/perl
-Mblib=/build/buildd/libdbi-
perl-1.58/blib;timeout=10;dsn=dbi:DBM:dbm_type=SDBM_File;lockfile=0','',...)
failed: DBD::Gofer receive_response timed-out after 10 seconds; DBI
connect('transport=pipeone;policy=pedantic;perl=/usr/bin/perl
-Mblib=/build/buildd/libdbi-perl-1.58/blib;timeout=10;dsn=dbi:DBM:dbm_type=SDBM_File;lockfile=0','',...)
failed: DBD::Gofer receive_response timed-out after 10 seconds
at /build/buildd/libdbi-perl-1.58/blib/lib/DBI/Gofer/Execute.pm line 194
at ./t/85gofer.t line 131 # ' # in ./t/85gofer.t at line 92.
What could be the reason?
The autobuilder usually uses some kind of chroot environment and the m68k
one is certainly alsow very slow so it might hit a condition that is
unusual on a normal desktop machine.
Occams's razor: Could you hack the test to increase the timeout, so say
100, and try again?
Did not help. But the m68k architecture is no longer officially supported
by Debian, just autobuilded along with the other architectures, so it's no
big deal :)
bye,
-christian-
Attachment:
signature.asc
Description: PGP signature
- References:
- Test t/85gofer.t fails on m68k
- From: Christian Hammers
- Re: Test t/85gofer.t fails on m68k
- From: Tim Bunce
- Test t/85gofer.t fails on m68k
- Prev by Date: Re: make test for DBI fails on Win98
- Next by Date: DBI::Informix and DBD::Informix
- Previous by thread: Re: Test t/85gofer.t fails on m68k
- Next by thread: DBI doc curiosity
- Index(es):