On Sat, 22 Aug 2026, 17:21 Sven Geuer, <[email protected]> wrote: > Hi Richard, > > On Sat, 22 Aug 2026 12:40:52 +0100 Richard Lewis < > [email protected]> wrote: > > On Thu, 20 Aug 2026 at 19:25, Paul Gevers <[email protected]> wrote: > > > > > I looked at the results of the autopkgtest of your package. I noticed > > > that it regularly fails, at least on s390x. I triggered 5 runs and 2 > > > failed. > > [...] > > > > I think what is happening is that a running (and unrelated) sshd is > > sometimes visible from the testbed and sometimes not (which influences > > the output). The autopkgtest wrongly assumed it would be consistent . > > i assume different test runners have different settings and that's why > > it looks flaky > > Looking at https://ci.debian.net/packages/c/chkrootkit/testing/s390x/ > it seems the issue is related to the incus-lxc backend, introduced > after 2026-07-30 22:13:25 UTC. Earlier tests, run on lxc, passed.
thanks -- looking at https://wiki.debian.org/ContinuousIntegration/LxcToIncus the lxc backend incldues sshd (!) it's correctly missing from incus. except isnt this one https://ci.debian.net/data/autopkgtest/testing/s390x/c/chkrootkit/74450913/log.gz is incus and passing. And there's not anything obviously arch-specific about this -- we should be seeing all the other arch's being equally flaky, and they dont seem to be. (if anyone can reproduce the failure, i would be curious to see what bash -xv chkrootkit sshd ps ax | grep sshd return on a s390 system where it fails) (But looking further: I dont actually see how the message seen on s390 could ever be produced in a functioning system --- it would need "ps ax sshd | grep -E sshd" to _fail_, which is never going to happen: the grep will match its own process in the output of ps (which is a bug in chkrootkit - but this is offset by a second bug as the test is backwards... luckily this only affects systems with a rootkit in sshd..... and there's a 3rd issue in that 'chkrootkit -q sshd' never reports anything ). so something else is perhaps broken/flaky in s390, but i suspect fixing the issues in chkrootkit and its tests will probably resolve the failure)
