HI Paul On Do 08 Apr 2021 09:15:17 CEST, Paul Gevers wrote:
Hi, On 08-04-2021 08:40, Mike Gabriel wrote:FAIL: ./test-libdbustest-mock FAIL test-libdbustest-mock-test (exit status: 1)This is a known issue for DBus unit tests in CI / buildd infrastructures. (I don't remember the full details / the bug number, but it is a problem caused by the interplay of libpam-systemd and schroot. Hmmm... maybe something similar is happening in lxc based builds (autopkgtests use lxc, iirc)?ci.debian.net is using lxc, yes, autopkgtest has much more backends.We could try bumping the debhelper compat level to version 13 (currently 11). That helped with libqtdbustest and libqtdbusmock a few months back. Would that be an RT compliant solution?https://release.debian.org/bullseye/FAQ.html last paragraph. So, what in compat level 13 is different for you that actually fixes the issue? Obviously if you can show in the necessary unblock request that the *only* delta of bumping compat level is the part that fixes this bug, we'd accept. But that would require you to e.g. run diffoscope on a build with and a build without the bump, as we can't judge the changes from source alone. Paul
I have now uploaded a dbus-test-runner with minimal changes to experimental (dbus-test-runner_16.10.0~bzr100+repack1-5~exp1).
Can you re-run those autopkgtests multiple times on ppc64el and check if the flakiness has now vanished with debhelper compat level bumped to version 13? Thanks.
Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
pgpFaTWovaUrM.pgp
Description: Digitale PGP-Signatur
