> On the remaining Linux architectures, the http test times out, perhaps
> due to idiosyncracies of buildd network configuration:
> !!!::req1 (2): Connection refused by host 'localhost' port '8086'
> error flushing "sock949f8a8": socket is not connected!!!
> xocomm/test.001: incorrect result for 'Trying to load image
logo-100.jpg ... ', expected:
> '1', got
> "0"
Mmmh. I tested in my build environments in various configurations
(amd64, i386). the connection tests suceed. How can I learn more about
these buildd limitations you hinted at? Are certain ports locked down
etc.? If I cannot ship around those limitations, what is the
authoritative approach then: disable these network I/O tests?
https://wiki.debian.org/buildd
says one should not rely on any network (interface) being available, so
(conditionally) disabling those tests is the way to go?
Stefan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
