I think this was likely a problem (race condition) in the upstream test
itself. I think I've been able to eliminate any races in the test with
upstream commits r3488 and r3489.
** Also affects: apparmor
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apparmor
Status: New => Fix Committed
** Changed in: apparmor
Assignee: (unassigned) => Tyler Hicks (tyhicks)
** Changed in: apparmor
Importance: Undecided => Medium
** Changed in: apparmor
Milestone: None => 2.11
** Also affects: apparmor (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1528230
Title:
[ADT test failure] linux: ubuntu_qrt_apparmor.test-apparmor.py --
ONEXEC - check current 'unconfined' != expected
Status in AppArmor:
Fix Committed
Status in QA Regression Testing:
Invalid
Status in apparmor package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in apparmor source package in Xenial:
In Progress
Status in linux source package in Xenial:
Invalid
Bug description:
New ADT test failure in Vivid:
running onexec
ONEXEC - check current 'unconfined' != expected
'/tmp/testlibIUFsmN/source/vivid/apparmor-2.9.1/tests/regression/apparmor/onexec'
Fatal Error (onexec): Unable to run test sub-executable
Full log:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-vivid/vivid/ppc64el/l/linux/20151218_175610@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1528230/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
