On Thu, 2018-08-30 at 13:23 +0100, Martín Ferrari wrote: > > 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.
> Right, but this can't be done without root, and buildds do not give root. I don't think that applies to the "needs to use a random port or otherwise be tollerant of 9090 not being available" which was the main thrust of my comment. > > Maybe there is (or should be) an autopkgtest flag to request a clean > > netns be used? > > This discussion is about a FTBFS bug, not about the CI system. ALso, > that would not solve the issue, as it is autopkgtest installing (and > therefore starting) prometheus. So the issue is a parallel (but unrelated) autopkgtest run on the same host interfering with builds which are happening at the same time? (I had thought the autopkgtest was part of the build hence → FTBFS, seems I was misunderstanding then, sorry for the noise on that front) Ian.