For $deity's sake, it failed again:
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
questing/questing/armhf/p/python-dbusmock/20251007_155821_7a4f9@/log.gz
186s autopkgtest [15:58:06]: test upstream: [-----------------------
188s ln: No such file or directory
188s /usr/sbin/apparmor_parser
Whatever that means.. apparmor is installed, but something is missing?
At first I thought it's the missing target dir /etc/apparmor.d/disable/
, but (1) ln fails differently then:
❱❱❱ ln -s README.md foo/bar/
ln: failed to create symbolic link 'foo/bar/': No such file or directory
and (2) the test went past that `ln` stage in earlier runs, and failed in
apparmor_parser.
As this is so utterly hard to debug, and I don't want to upload 5 more
attempts to Debian unstable, I'll think of something different. Like,
skipping that whole libnotify test in Ubuntu, as the new AppArmor
profile breaks mocking anyway.
** Changed in: python-dbusmock (Ubuntu)
Status: Fix Committed => Confirmed
** Summary changed:
- python-dbusmock autopkgtest failures
+ python-dbusmock autopkgtest failures on LXD runners
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2121092
Title:
python-dbusmock autopkgtest failures on LXD runners
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-dbusmock/+bug/2121092/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
