test_072_strict_devmem in ubuntu_qrt_kernel_security failed to build with 5.0 hwe-edge kernel on BIonic

[Po-Hsu Lin]

This might have something to do with bug 1823994
Test failed to bulild with header not found issue

======================================================================
FAIL: test_072_strict_devmem (__main__.KernelSecurityTest)
/dev/mem unreadable for kernel memory
----------------------------------------------------------------------
Traceback (most recent call last):
  File "./test-kernel-security.py", line 614, in test_072_strict_devmem
    self.assertShellExitEquals(0, ["make"])
  File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1140, in assertShellExitEquals
    self.assertEqual(expected, rc, msg + result + report)
AssertionError: Got exit code 2, expected 0
Command: 'make'
Output:
cc -Wall -Werror -O2 readmem.c -o readmem -lcap
make -C signpost
make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/mem/signpost'
make -C /usr/src/linux-headers-5.0.0-8-generic SUBDIRS=$PWD modules
make[2]: Entering directory '/usr/src/linux-headers-5.0.0-8-generic'
make[2]: Makefile: No such file or directory
make[2]: *** No rule to make target 'Makefile'. Stop.
make[2]: Leaving directory '/usr/src/linux-headers-5.0.0-8-generic'
Makefile:4: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/mem/signpost'
Makefile:6: recipe for target 'all' failed
make: *** [all] Error 2

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1825145

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Connor Kuehl (connork)]

I don't see this failure in our test results for the Bionic 5.0 kernel any more and I also don't see it in the Bionic 5.3 kernel.