On Wed, Feb 14, 2024 at 23:15:59 +0000, Mathias Gibbens wrote: > On Wed, 2024-02-14 at 18:44 +0100, Simon Josefsson wrote: > > This problem happens for others: > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063746 > > > > Interestingly the failure seems arch-specific: > > > > https://ci.debian.net/packages/g/golang-github-katalix-go-l2tp/ > > > > It could still well be that something in salsa and debci VM, and the > > #1063746 reporter's machine, that is causing this -- but it seems this > > clearly happens often enough, and is causing build failures checking > > reverse dependencies of several packages going into experimental, so it > > would be nice to fix it. Do you have any ideas? Could some test be > > disabled or silenced somehow? I'm ignoring build failures in > > golang-github-katalix-go-l2tp meanwhile. > > My build server is an older Xeon with ECC RAM, running bookworm. I > use LXD (soon to be Incus) to create various containers; for > determining FTBFS issues I have a sid container which in turn contains > a sid schroot. The only other bit of potential interesting information > is that my containers are configured to only have IPv6 connectivity. Hi Mathias, Thank you for the further information. I've been digging into this issue a bit more today and it appears to be a kernel problem of some kind. I've not quite got to the bottom of it as yet, but I have reproduced the basic issue on bookworm now, and I can see packets on the wire, but they're malformed and hence not getting through to the receiver socket. Keeping the golang env the same, and the go-l2tp version the same, I find that on older kernels this doesn't seem to be an issue, but on later ones it is :-/ If I'm correct, and it is a kernel issue, I'll have to make a go-l2tp mod to skip this test in certain configurations. Once I've figured out exactly what's going on I'll patch go-l2tp if appropriate. Thanks, Tom
Attachment:
signature.asc
Description: PGP signature