On 14/07/16 at 19:04 -0700, Russ Allbery wrote: > Lucas Nussbaum <lu...@debian.org> writes: > > > Source: lbcd > > Version: 3.5.2-1 > > Severity: serious > > Tags: stretch sid > > User: debian...@lists.debian.org > > Usertags: qa-ftbfs-20160707 qa-ftbfs > > Justification: FTBFS on amd64 > > > During a rebuild of all packages in sid, your package failed to build on > > amd64. > > >> util/network/client.....FAILED 21-22 > > Hi Lucas, > > It looks like there's something about your testing environment that causes > problems with network timeouts. You reported two bugs like this against > two of my packages that include the same network code and run the same > test, and it failed the same way in both cases. Both test an attempted > network action against a local server spun up by the same test that > doesn't respond. > > The failure you saw here was not reproducible locally or in a Debian > unstable chroot, so I prepared a new version of lbcd and uploaded it to > see if the buildd environment was different. But the build and test also > succeeds on all the Debian buildds. > > Given that, I'm closing this as a false positive that I can't reproduce, > but if you have any additional information that indicates this is wrong, > please do let me know.
Hi, I found the source (or more exactly: Antonio Terceiro and Eric Wong did in #830353). It seems that the Debian EC2 image uses non-default TCP buffer sizes. (see https://lists.debian.org/20160719211715.ga8...@xanadu.blop.info ) When setting them back to the default value, both lbcd and remctl build fine. Lucas
