[pkg-go] Bug#907171: prometheus FTBFS:
Ian Campbell
ijc at debian.org
Thu Aug 30 09:51:56 BST 2018
On Mon, 2018-08-27 at 19:18 +0100, MartÃn Ferrari wrote:
> On 27/08/18 17:08, Adrian Bunk wrote:
>
> > How often did you try?
> >
> > I would say the probability to hit is somewhere around 50%:
> > https://tests.reproducible-builds.org/debian/history/prometheus.html
>
> I just tried 20 builds, while using desktop applications that put some
> extra strain on tHE CPU, and none failed..
Port 9090 isn't reserved or privileged at all afaik so it's not out of
the question that some other random outgoing socket connection might be
using it as a source port (or listening on it) at any given point,
whether it is prom running on the host or something else.
Does `nc -l -p 9090` repro the test failure perhaps?
Unless the tests are run in their own network namespace (which provides
some guarantees over what else might be bound to a port, I can't seem
to find logs which would confirm or deny if a netns was in use here
though) probably the test needs to use a random port or otherwise be
tollerant of 9090 not being available.
Maybe there is (or should be) an autopkgtest flag to request a clean
netns be used?
Ian.
More information about the Pkg-go-maintainers
mailing list