Comment 0 for bug 2062138

This issue can be found on M-generic 6.5.0-34.34 and M-lowlatency 6.5.0-27.28.1 on Azure instance Standard_A2_v2

The test-logprof.py test from ApparmorTestsuites.test_utils_testsuite and test_utils_testsuite3 failed with:
$ sudo python3 ./test-logprof.py
E
======================================================================
ERROR: test_0 (__main__.TestLogprof.test_0)
test 'ping'
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/tmp/mine/source/mantic/apparmor-4.0.0~alpha2/utils/test/common_test.py", line 90, in stub_test
    self._run_test(test_data, expected)
  File "/tmp/mine/source/mantic/apparmor-4.0.0~alpha2/utils/test/./test-logprof.py", line 99, in _run_test
    self.process.wait(timeout=0.2)
  File "/usr/lib/python3.11/subprocess.py", line 1264, in wait
    return self._wait(timeout=timeout)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/subprocess.py", line 2038, in _wait
    raise TimeoutExpired(self.args, timeout)
subprocess.TimeoutExpired: Command '['/usr/bin/python3', '../aa-logprof', '--json', '--configdir', './', '-f', './logprof/ping.auditlog', '-d', '/tmp/aa-test-7feu1ddr/profiles', '--no-check-mountpoint']' timed out after 0.2 seconds

----------------------------------------------------------------------
Ran 1 test in 1.831s

FAILED (errors=1)

The fail rate is almost 100%, 3 successful out of 100 attempts

If you bump the timeout to 0.3 and it will pass. We need this patch:
https://gitlab.com/apparmor/apparmor/-/commit/dd9b7b358f0dd0887767a5840ed7f7499aa50ee6