For the apparmor failure, this is caused by /usr/bin/python being a
symlink to python2, which is in turn a symlink to python2.7, which
caught the tests unprepared to handle nested symlinks like that. A fix
has been proposed at
https://gitlab.com/apparmor/apparmor/merge_requests/147 and committed to
The CONFIG_CC_STACKPROTECTOR issue was addressed in bug 1776242, leaving
the apparmor test failure to resolve.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779314
Title:
linux 4.17.0-3.4 ADT test
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Also affects: qa-regression-testing
Importance: Undecided
Status: New
** Also affects: apparmor
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bu
Second failure:
==
FAIL: test_7 (__main__.AaTest_get_interpreter_and_abstraction)
test '#!/usr/bin/python'
--
Traceback (most recent call last):
Fil
First failure:
==
FAIL: test_075_config_stack_protector (__main__.KernelSecurityTest)
CONFIG_CC_STACKPROTECTOR set
--
Traceback (most recent call last):
