Test t/85gofer.t fails on m68k

--Sig_V=2blCit=GSe6vXUx.fm0zh
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

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=3Dnull;policy=3Dpedantic;=
dsn=3Ddbi:Gofer:transport=3Dpipeone;policy=3Dpedantic;perl=3 D/usr/bin/perl =
-Mblib=3D/build/buildd/libdbi- perl-1.58/blib;timeout=3D10;dsn=3Ddbi:DBM=
:dbm_type=3DSDBM_File;lockfile=3D0','',...) failed: DBD::Gofer receive_resp=
onse timed-out after 10 seconds; DBI connect('transport=3Dpipeone;policy=3D=
pedantic;perl=3D/usr/bin/perl -Mblib=3D/build/buildd/libdbi-perl-1.58/blib=
;timeout=3D10;dsn=3Ddbi:DBM:dbm_type=3DSDBM_File;lockfile=3D 0','',...) fail=
ed: 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 l=
ine 131
# '
# in ./t/85gofer.t at line 92.

What could be the reason?=20

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=20
unusual on a normal desktop machine.

bye,

-christian-

--Sig_V=2blCit=GSe6vXUx.fm0zh
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iEYEARECAAYFAkbIf2IACgkQkR9K5oahGOak+QCeNfXeMjseuLdcXCZilyVW b/WB
ABIAnirrLkalcs824KZ2hogs5YvZ9PTa
=loP1
-----END PGP SIGNATURE-----

--Sig_V=2blCit=GSe6vXUx.fm0zh--

Re: Test t/85gofer.t fails on m68k

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:transp ort=pipeone;policy=pedantic;perl=/usr/bin/perl -Mblib=/build/buildd/libdbi- perl-1.58/blib;timeout=10;dsn=dbi:DBM:dbm_type=SDBM_File;loc kfile=0','',...) failed: DBD::Gofer receive_response timed-out after 10 seconds; DBI connect('transport=pipeone;policy=pedantic;perl=/usr/bin/per l -Mblib=/build/buildd/libdbi-perl-1.58/blib;timeout=10;dsn=db i: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?

Tim.

Re: Test t/85gofer.t fails on m68k

--Sig_bK2YPShbFfe/q.rFEWfU4L+
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hello

On 2007-08-20 Tim Bunce wrote:
> On Sun, Aug 19, 2007 at 07:35:28PM +0200, Christian Hammers wrote:
> > Hello
> >=20
> > The Debian autobuilders for arm and m68k fail while trying test
> > t/85gofer.t with the following messages:
> >=20
> > t/zvxgp_85gofer...........
> > # Failed test 'pipeone: DBI
> > connect('transport=3Dnull;policy=3Dpedantic;dsn=3Ddbi:Gofer: transport=
=3Dpipeone;policy=3Dpedantic;perl=3D/usr/bin/perl
> > -Mblib=3D/build/buildd/libdbi-
> > perl-1.58/blib;timeout=3D10;dsn=3Ddbi:DBM:dbm_type=3DSDBM_Fi le;lockfile=
=3D0','',...)
> > failed: DBD::Gofer receive_response timed-out after 10 seconds; DBI
> > connect('transport=3Dpipeone;policy=3Dpedantic;perl=3D/usr/b in/perl
> > -Mblib=3D/build/buildd/libdbi-perl-1.58/blib;timeout=3D10;ds n=3Ddbi:DBM=
:dbm_type=3DSDBM_File;lockfile=3D0','',...)
> > 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.
> >=20
> > What could be the reason?=20
> >=20
> > The autobuilder usually uses some kind of chroot environment and the m6=
8k
> > one is certainly alsow very slow so it might hit a condition that is=20
> > unusual on a normal desktop machine.
>=20
> 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-

--Sig_bK2YPShbFfe/q.rFEWfU4L+
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iEYEARECAAYFAkbTTHgACgkQkR9K5oahGOZk0gCfQvKgFsN9XFWsQf2PIlVP tIo0
ps8An3Vgn5URKAUA8/82wpwahMY0eWdl
=FSA/
-----END PGP SIGNATURE-----

--Sig_bK2YPShbFfe/q.rFEWfU4L+--