Source: bilibop Version: 0.6.3 Severity: important User: debian...@lists.debian.org Usertags: isolation-machine
Dear maintainer(s),Your package has an autopkgtest, great. I recently added support for isolation-machine tests on ci.debian.net for amd64 and added your package to the list to use that. However, it fails on bookworm, trixie and unstable (it passes on buster). Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report.
The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing, but because machine-isolation support by ci.debian.net is new I have not marked this bug as serious (yet).
More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html https://ci.debian.net/packages/b/bilibop/testing/amd64/41366843/ 135s autopkgtest [21:30:14]: test lockfs: [----------------------- 135s # grep -E ' / |overlay|lockfs|aufs' /proc/mounts 135s /dev/vda1 / ext4 rw,relatime,errors=remount-ro 0 0 135s 135s # lsblk --output=name,ro,mountpoint 135s NAME RO MOUNTPOINT 135s fd0 0 135s sr0 0 135s vda 0 135s └─vda1 0 / 135s 135s # df --output=source,fstype,target 135s Filesystem Type Mounted on 135s udev devtmpfs /dev 135s tmpfs tmpfs /run 135s /dev/vda1 ext4 / 135s tmpfs tmpfs /dev/shm 135s tmpfs tmpfs /run/lock 135s autopkgtest 9p /run/autopkgtest/shared 135s tmpfs tmpfs /run/user/0 135s 135s STAGE 0: root filesystem is not locked. 135s STAGE 0: enable bilibop-lockfs and reboot. 135s 135s # echo BILIBOP_LOCKFS='true' | tee /etc/bilibop/bilibop.conf 135s BILIBOP_LOCKFS=true 135s 135s # sync 135s 135s Killed136s autopkgtest [21:30:15]: test process requested reboot with marker lockfs
154s # grep -E ' / |overlay|lockfs|aufs' /proc/mounts 154s tmpfs /overlay tmpfs rw,relatime,mode=755,inode64 0 0 154s /dev/vda1 /overlay/ro ext4 ro,relatime 0 0154s overlay / overlay rw,relatime,lowerdir=/overlay/ro,upperdir=/overlay/rw,workdir=/overlay/.rw 0 0
154s 154s # lsblk --output=name,ro,mountpoint 154s NAME RO MOUNTPOINT 154s fd0 0 154s sr0 0 154s vda 1 154s └─vda1 1 /overlay/ro 154s 154s # df --output=source,fstype,target 154s Filesystem Type Mounted on 154s udev devtmpfs /dev 154s tmpfs tmpfs /run 154s tmpfs tmpfs /overlay 154s /dev/vda1 ext4 /overlay/ro 154s overlay overlay / 154s tmpfs tmpfs /dev/shm 154s tmpfs tmpfs /run/lock 154s autopkgtest 9p /run/autopkgtest/shared 154s tmpfs tmpfs /run/user/0 154s154s mount: /overlay/ro: cannot remount /dev/vda1 read-write, is write-protected. 154s dmesg(1) may have more information after failed mount system call.
154s STAGE 1: root filesystem is successfully locked with hard policy. 154s STAGE 1: change lockfs settings and reboot. 154s 154s # blockdev -v --setrw /dev/vda1 154s set read-write succeeded. 154s 154s # mount -v -o remount,rw /overlay/ro 155s autopkgtest [21:30:34]: test lockfs: -----------------------]155s autopkgtest [21:30:34]: test lockfs: - - - - - - - - - - results - - - - - - - - - -
155s lockfs FAIL non-zero exit status 32
OpenPGP_signature.asc
Description: OpenPGP digital signature
