linux: intermittent ADT test failures on ppc64el

[Andy Whitcroft]

The linux internal test suites fail intermittently (1/3 approx) as below:

[...]
  test_parser_testsuite (__main__.ApparmorTestsuites)
  Run parser regression tests ... ok
  test_regression_testsuite (__main__.ApparmorTestsuites)
  Run kernel regression tests ... FAIL
  test_stress_parser_testsuite (__main__.ApparmorTestsuites)
  Run parser stress test ... ok
[...]
  ======================================================================
  FAIL: test_regression_testsuite (__main__.ApparmorTestsuites)
  Run kernel regression tests
  ----------------------------------------------------------------------
  Traceback (most recent call last):
    File "./test-apparmor.py", line 1589, in test_regression_testsuite
      self.assertEquals(expected, rc, result + report)
  AssertionError: Got exit code 2, expected 0

[Andy Whitcroft (apw)]

History:

    http://autopkgtest.ubuntu.com/packages/l/linux/xenial/ppc64el/

[Steve Beattie (sbeattie)]

Looking at the history I'm seeing two different infrequent failures from the apparmor regression tests.

(1) an onexec test problem:

  running onexec
  ONEXEC - check current 'unconfined' != expected '/tmp/testlib_3WfLd/source/xenial/apparmor-2.10/tests/regression/apparmor/onexec'
  Fatal Error (onexec): Unable to run test sub-executable

(2) an exec_qual test failure or problem:

  running exec_qual
  /tmp/testlibk354G3/source/xenial/apparmor-2.10/tests/regression/apparmor/prologue.inc: line 184: 26766 User defined signal 1 $testexec "$@" > $outfile 2>&1
  Error: exec_qual failed. Test 'enforce px case4' was expected to 'fail'. Reason for failure 'killed by signal 10'

[Tyler Hicks (tyhicks)]

The (1) onexec test problem is tracked in bug #1528230. Please use this bug to track the (2) exec_qual test failure or problem.