On Wed, 22 Dec 2021 21:02:37 +0100, Lucas Nussbaum wrote: > > Do you have any idea how this can happen in your test environment or > > any information for us, what is special about it? > I tried it again and could reproduce it.
Thank your very much for taking the extra time to further investigate this issue! > I think that what happens is: > 1/ the VM hostname is set to ip-10-84-232-230 (or ip-10-84-232-242 in the > bug report) > 2/ /etc/hosts is correctly configured to resolve that hostname: > 127.0.1.1 ip-10-84-232-230.eu-central-1.compute.internal ip-10-84-232-230 > 3/ however, schroot does not copy /etc/hosts into the chroot. The > content of /etc/hosts in the chroot does not include the line for 127.0.1.1. > 4/ when the test suite runs traceroute on the machine's hostname, > traceroute fails to resolve the hostname, and exits with exit code 2. That makes totally sense. > 5/ for some reason, the test harness thinks the test exited with code 255. I guess that's becaucse the module code itself has | die "No output from traceroute. Exec failure?" and the actual tests aren't even run as instantiating the module already fails. > libnet-traceroute-perl seems to be the only package failing to build due > to this condition, so it might be worth fixing in the package, even if > one could argue that it's a bug in the build environment. Maybe > tracerouting to 127.0.0.1 would be enough? Yeah, that might be viable option. Thanks again, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Alan Jackson: Chattahoochee
signature.asc
Description: Digital Signature