On Fri, Oct 23, 2020 at 09:35:09AM +0200, Kurt Roeckx wrote: > Date: Thu, 22 Oct 2020 21:20:37 -0700 > From: Nicholas Breen <nbr...@debian.org> > To: am...@buildd.debian.org > Subject: buildd host x86-conova-01 - connections to localhost during build? > User-Agent: Mutt/1.9.4 (2018-02-28) > > Hello, > > Part of the test suite for src:gromacs launches a MPI process that > connects to localhost. On the recently (?) added buildd x86-conova-01 > *only*, this fails: > > 2: Test command: /usr/bin/mpiexec.mpich "-np" "2" "-host" "localhost" > "/<<PKGBUILDDIR>>/build/mpich/bin/testutils-mpi-test" > "--gtest_output=xml:/<<PKGBUILDDIR>>/build/mpich/Testing/Temporary/TestUtilsMpiUnitTests.xml" > [...] > 2: MPID_nem_tcp_init(373).............: gethostbyname failed, localhost > (errno 0) > > This test passes on the other amd64 buildd hosts and the hosts for other > architectures. The build logs don't narrow down the exact problem any > further than that. Can x86-conova-01 please be configured similarly to > the other hosts in this regard, or alternatively, can gromacs be > blacklisted on it? > > I anticipate the same would happen on an i386 build, but it hasn't come > up yet. > That is probably related to x86-conova-01 not having a (non-loopback) ipv4 address.
See https://lists.debian.org/debian-devel/2020/07/msg00070.html Cheers, Julien
