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 hope I copy/pasted the relevant part below.
> Don't hesitate to reach out if you need help and some more information > from our infrastructure. > https://ci.debian.net/packages/c/chkrootkit/testing/s390x/74480411/ > 532s Missing: ^Checking `sshd'\.\.\. > INFECTED but disabled$ > 532s *** Unexpected (unmatched) lines follow (for info): > 532s Checking `sshd'... INFECTED 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 But i think there's some other issue that needs a bit more investigating by me (i will loook in the next 2 weeks): - how can sshd ever be visible from the testbed? - why doesnt the following test with -q fail in the same way. - (is the upstream code for seeing if sshd is running correct? ) (nb - add a "ps ax" to the info section at the start of the test to have more info about the testbed!)
