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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528230 Title: [ADT test failure] linux: ubuntu_qrt_apparmor.test-apparmor.py -- ONEXEC - check current 'unconfined' != expected To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1528230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs