Bug#1035983: libsoap3 (and libsoap2) autopkgtests are flaky: Address already in use: AH00072: make_sock: could not bind to address 127.0.0.1:47524
Luca Boccassi
bluca at debian.org
Fri Jan 24 11:40:49 GMT 2025
Control: severity -1 grave
On Mon, 2 Dec 2024 15:51:14 +0300 Michael Tokarev <mjt at tls.msk.ru>
wrote:
> On Fri, 6 Sep 2024 07:46:28 -0400 Jeremy Bícha
<jeremy.bicha at canonical.com> wrote:
>
> > For reference, it looks like the autopkgtests are not failing so
> > frequently as to be especially problematic.
>
> I re-scheduled libsoap3 autopkgtest on s390x 2 times in a row for
current samba-triggered run.
> It failed again. Should I keep re-scheduling it until success?
>
> Note there are 6 failures like this just in the single last attempt:
> https://ci.debian.net/packages/libs/libsoup3/testing/s390x/54980275/
>
> Hmm..
Same experience with src:systemd uploads.
RT says that flaky autopkgtest are RC, so raising severity accordingly.
Restrictions: flaky could also be added if the tests can't be fixed, as
a quick bandaid.
More information about the pkg-gnome-maintainers
mailing list