Source: golang-github-katalix-go-l2tp
Version: 0.1.6-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs

In a clean sid schroot, one of the tests is timing out:

transport_test.go:388: test sender function reported an error: failed to send Hello message: transmit of avpMsgTypeHello failed after 3 retry attempts
panic: test timed out after 10m0s
running tests:
TestBasicSendReceive (9m59s)
TestBasicSendReceive/5:_send/recv_[::1]:9000_[::1]:9001_L2TPv3_IP (9m59s)

[snip goroutine tracebacks]

This is also occurring in the debci runs: https://ci.debian.net/packages/g/golang-github-katalix-go-l2tp/

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEE1Bp60H32xfynSJ8cKe7i1uz0QvkFAmXJWdYACgkQKe7i1uz0 Qvk6Tw/9ENgLD7Dc0MkODdBbqRSaU+oM+EPqztnK+V/e7MeuFtmqqsXbv8e91oH0 YahYTE0RKDEGhbNyUoqmwvqv/oYgmM6OonEwd4fFXPQsY/bhAYRG+CHB1YZZyM69 PJo0JH7+TiPaorB3LKkNdIufWz+uFvZz+70msfl8oQRWF0bz8lNzIyVidJIsfdTY Qn94Wxm5NV9wrKPqLg5gdvJ4x9/iGaN8RupKscsrgo1364aURudqq1CwIjj1gkDS zDfeGApl1Epso/6WEGqPSZoCPJAYPgTMtJzPmBdKuKlJD+mO10ZHDhyX6RkbeBtO jYjKcpkroz3QwgrIzeO2yT/Nmcl+RHdjhRBLGm8O8vpJVhKaKZwvqAU5207lnl02 w7mp5ErhSAXuPhla06YmUKqI3MgGFj3vm0QXoD5azLHmB5dKiFwFfLIFLY16e41T tZg+TXTgJGr8bk1iATuAoTqOq0XMCslaYzL/8kalrLNq25qB3SFw6MiiuBJskneh xHfNuUabOkh6ZqTvIu+ZWtm2ixaFqHwR0gtNEI3zYeodnjT/YNBworiHxX+8xCEw x2fu78Yd07pPOp1zuN1lMbX3jYr2u9dHUP7T4jbMK6Vh4RXNULtTEU3EBUfVhQgD cpf06Ul64fMVsb9Jez9xMnPovBH15EA0uVB1LDp2zQc1ce7OrQU=
=Up1d
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format...

Your message dated Tue, 20 Feb 2024 10:04:34 +0000
with message-id <E1rcMzK-00HVym-4X@fasolo.debian.org>
and subject line Bug#1063746: fixed in golang-github-katalix-go-l2tp 0.1.7-1 has caused the Debian Bug report #1063746,
regarding golang-github-katalix-go-l2tp: FTBFS: transport_test.go:388: test sender function reported an error: failed to send Hello message: transmit of avpMsgTypeHello failed after 3 retry attempts
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


--
1063746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063746
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Received: (at submit) by bugs.debian.org; 11 Feb 2024 23:35:58 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
(2021-04-09) on buxtehude.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-110.9 required=4.0 tests=BAYES_00,DKIMWL_WL_HIGH,
DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,
PGPSIGNATURE,SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE,
UNPARSEABLE_RELAY,USER_IN_DKIM_WELCOMELIST,USER_IN_DKIM_WHITELIST
autolearn=ham autolearn_force=no
version=3.4.6-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 14; hammy, 137; neutral, 20; spammy,
0. spammytokens:
hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
0.000-+--H*RT:108, 0.000-+--H*RT:311
Return-path: <gibmat@debian.org>
Received: from stravinsky.debian.or