Hi Paul, On Mi 07 Apr 2021 21:20:55 CEST, Paul Gevers wrote:
Source: dbus-test-runner Version: 16.10.0~bzr100+repack1-4.1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org, t...@canonical.com User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), Your package has an autopkgtest, great. However, I looked into the history of your autopkgtest [1] and I noticed the it fails regularly on ppc64el, while a rerun passes. I copied some of the output at the bottom of this report. As far as I checked, it's always the same issue. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Paul [1] https://ci.debian.net/packages/d/dbus-test-runner/testing/ppc64el/ https://ci.debian.net/data/autopkgtest/testing/ppc64el/d/dbus-test-runner/11196676/log.gz 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)?
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? 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
pgp6r2FiimofH.pgp
Description: Digitale PGP-Signatur
