On Tue, Feb 25, 2025 at 02:54:03PM +0100, Christian Hofstaedtler wrote: > * Ferenc Wágner <wf...@debian.org> [250225 14:11]: > > Valentin Vidic <vvi...@debian.org> writes: > > > On Sun, Feb 23, 2025 at 01:13:14PM +0100, Chris Hofstaedtler wrote: > > > > > >> It appears the test is flaky, a retry passed: > > >> > > >> https://ci.debian.net/packages/d/dlm/unstable/amd64/58083508/ > > >> > > >> Please investigate and/or mark the test as flaky. > > > > > > I cannot reproduce the problem locally unfortunately. The only > > > strage thing I see in the logs is failing to start the service > > > after installation: > > > > > > 191s Setting up dlm-controld (4.3.0-1+b1) ... > > > 192s Created symlink > > > '/etc/systemd/system/multi-user.target.wants/dlm.service' → > > > '/usr/lib/systemd/system/dlm.service'. > > > 202s Could not execute systemctl: at /usr/bin/deb-systemd-invoke line > > > 148. > > > > > > Since the test expects the service to be running, that would > > > explain the test failure. But it is not clear why the service > > > failed to start in the first place. > > > > Is the VM running the test managed by systemd? > > What is its kernel version? > > I don't know, but I'll gladly CC: debian...@lists.debian.org.
All tests on ci.debian.net run on a Debian system with its default init system (systemd). dlm specifically is configured to use QEMU, so it will run on a QEMU VM running whatever kernel is was the one present in unstable at that time. The test linked above says this in its logs: 57s autopkgtest [12:08:19]: testbed running kernel: Linux 6.12.15-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.15-1 (2025-02-18) > I'll note that relying on a specific init is discouraged by the > autopkgtest docs. The same might be true for the kernel version, but > thats also something for debian-ci@. Well, kernel-related packages cannot ignore the kernel, and this is why we have QEMU support so those get tested with the kernel from the same suite as the package being tested.
signature.asc
Description: PGP signature
