It looks like this hang issue was introduced because the mmap test has timed out. And it gets killed by the autotest framework.
However it's not really "killed", you can see that it's still stuck with mmap test:
# ps aux root 23787 0.0 0.0 4384 748 ? S 06:21 0:00 /tmp/testlibpIXHkr/source/bionic/apparmor-2.12/tests/regression/apparmor/mmap
# ps aux |grep Z USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND ubuntu 2138 0.0 0.0 0 0 ? Z 05:48 0:00 [sh] <defunct> root 8307 0.0 0.0 0 0 ? Z 10:15 0:00 [unix_socket_cli] <defunct>
In this case, with PID 23787 killed, the test will keep going and terminates on jenkins properly.
It looks like this hang issue was introduced because the mmap test has timed out.
And it gets killed by the autotest framework.
However it's not really "killed", you can see that it's still stuck with mmap test:
# ps aux Hkr/source/ bionic/ apparmor- 2.12/tests/ regression/ apparmor/ mmap
root 23787 0.0 0.0 4384 748 ? S 06:21 0:00 /tmp/testlibpIX
# ps aux |grep Z
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
ubuntu 2138 0.0 0.0 0 0 ? Z 05:48 0:00 [sh] <defunct>
root 8307 0.0 0.0 0 0 ? Z 10:15 0:00 [unix_socket_cli] <defunct>
In this case, with PID 23787 killed, the test will keep going and terminates on jenkins properly.