Comment 0 for bug 2051227

Revision history for this message
Po-Hsu Lin (cypressyew) wrote : test_regression_mqueue_abi from ubuntu_qrt_apparmor is failing with 5.15 ARM64

Issue found on:
 * F-azure-5.15.0-1055.63~20.04.1 ARM64 Standard_D2pds_v5
 * F-aws-5.15.0-1053.58~20.04.1 ARM64 c6g.8xlarge
 * F-lowlatency-hwe-5.15.0-94.104~20.04.1 64k ARM64 openstack
 * F-hwe-5.15.0-94.104~20.04.1 64k ARM64 openstack

(We don't run this test on baremetal with F-hwe-5.15 / F-lowlatency-hwe-5.15)

Test failed with:
 Running 'python2 ./test-apparmor.py -v ApparmorTestsuites.test_regression_mqueue_abi'
 Running test: './test-apparmor.py' distro: 'Ubuntu 20.04' kernel: '5.15.0-1053.58~20.04.1 (Ubuntu 5.15.0-1053.58~20.04.1-aws 5.15.136)' arch: 'arm64' init: 'systemd' uid: 0/0 SUDO_USER: 'ubuntu')
 test_regression_mqueue_abi (__main__.ApparmorTestsuites)
 Skipping private tests

 Test if abi is working properly ... (Applying patch 0001-tests-regression-apparmor-syscall.sh-fail-iopl-ioper.patch) (Applying patch 0001-tests-regression-apparmor-capabilities.sh-fail-iopl-.patch) (Applying patch use-pyflakes3-with-2.13.patch) (Applying patch 0001-regression-tests-add-FIPS-140-2-lib-validation-hmac-.patch) FAIL

 ======================================================================
   preparing apparmor_2.13.3-7ubuntu5.3.dsc... done
 FAIL: test_regression_mqueue_abi (__main__.ApparmorTestsuites)
 Test if abi is working properly
 ----------------------------------------------------------------------
 Traceback (most recent call last):
   File "./test-apparmor.py", line 2055, in test_regression_mqueue_abi
     self.assertEqual(expected, rc, result + report)
 AssertionError: Got exit code 1, expected 0
 Unrecognized option

 Usage: /tmp/testlib4X340M/source/focal/apparmor-2.13.3/tests/regression/apparmor/posix_mq_rcv [options]
 Options are:
 -n get notified if there's an item in the queue
           available options are: mq_notify, select, poll and epoll
 -k message queue name (default is /testmq)
 -c path of the client binary
 -u run test as specified UID
 -t timeout in seconds

 ----------------------------------------------------------------------
 Ran 1 test in 20.176s

 FAILED (failures=1)

I can't reproduce this issue with 5.15.0-1053.61~20.04.1 on Standard_D2pds_v5