Source: bilibop Version: 0.6.1 Severity: important User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu groovy
Hi Yann, In your latest upload, you introduced a 'lockfs' autopkgtest. This test is skipped on Debian autopkgtest infrastructure because it has an 'isolation-machine' restriction. But in Ubuntu, the test is run, and fails on all architectures: [...] # df --output=source,fstype,target Filesystem Type Mounted on udev devtmpfs /dev tmpfs tmpfs /run tmpfs tmpfs /aufs/rw /dev/vda1 ext4 /aufs/ro aufs aufs / tmpfs tmpfs /dev/shm tmpfs tmpfs /run/lock tmpfs tmpfs /sys/fs/cgroup tmpfs tmpfs /aufs/rw/boot/efi /dev/vda15 vfat /aufs/ro/boot/efi aufs aufs /boot/efi tmpfs tmpfs /run/user/1000 STAGE 1: unexpected error autopkgtest [08:43:15]: test lockfs: -----------------------] autopkgtest [08:43:16]: test lockfs: - - - - - - - - - - results - - - - - - - - - - lockfs FAIL non-zero exit status 91 [...] (https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/b/bilibop/20200501_084325_e3c5c@/log.gz) I have not attempted to debug this; but it seems the test is not particularly useful at present, since it is not run in Debian and fails in Ubuntu. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: PGP signature
