Re: test failures for 2.2 on Debian buildd's

Dear David,

>=20
> I'm not sure what's going on, but on several architectures, including
> i386 (IA32 for intel employees ;)) the test "Testing auth permanent
> failure with smtp" seems to be hanging.  There isn't any interesting
> output in the logs, just
>=20
> Running test /<<PKGBUILDDIR>>/test/tests/smtp-auth...
> Testing auth success with smtp
> Testing auth login success with smtp
> Testing auth temporary failure with smtp
> Testing auth permanent failure with smtp
> E: Build killed with signal TERM after 150 minutes of inactivity

to me it seems some buildds fail earlier:

Testing auth login success with smtp
******************************Failed!******************************

Or is this just a difference in the output format?

>=20
> Does anyone have any idea what might be going on? These things are
> usually caused by network isolation on the build host, although I did
> verify (I think) that the client was able to connect to the server
> running on localhost. The other shenanigans that might be happening is
> that at least on some hosts where this fails, /bin is a symlink to
> /usr. This sometimes confuses configure, although it's not clear how
> that applies here.
>=20
> Failing clues, is there a way to turn on more verbose output for the
> tests?

Doing local compiles on amd64 I only succeeded so far by specifying nocheck=
 option.
Maybe some buildds have firewall rules while others don't?

>=20
> d
>=20

Kind regards
Harald Jenny