Public bug reported:
QRT is failing when run against the 6.14 kernel with the following trace
test_sock_dgram (__main__.ApparmorUnixDomainConnect.test_sock_dgram)
Test mediation of file based SOCK_DGRAM connect ... FAIL
test_sock_seqpacket (__main__.ApparmorUnixDomainConnect.test_sock_seqpacket)
Test mediation of file based SOCK_SEQPACKET connect ... FAIL
test_sock_stream (__main__.ApparmorUnixDomainConnect.test_sock_stream)
Test mediation of file based SOCK_STREAM connect ... FAIL
======================================================================
FAIL: test_sock_dgram (__main__.ApparmorUnixDomainConnect.test_sock_dgram)
Test mediation of file based SOCK_DGRAM connect
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/ryan-lee/qrt-test-apparmor/./test-apparmor.py", line 3698, in
test_sock_dgram
self._test_sock_type('dgram')
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^
File "/home/ryan-lee/qrt-test-apparmor/./test-apparmor.py", line 3694, in
_test_sock_type
self.assertEqual(expected, rc, result + report)
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 1 != 0 : Got exit code 0, expected 1
======================================================================
FAIL: test_sock_seqpacket
(__main__.ApparmorUnixDomainConnect.test_sock_seqpacket)
Test mediation of file based SOCK_SEQPACKET connect
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/ryan-lee/qrt-test-apparmor/./test-apparmor.py", line 3702, in
test_sock_seqpacket
self._test_sock_type('seqpacket')
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
File "/home/ryan-lee/qrt-test-apparmor/./test-apparmor.py", line 3694, in
_test_sock_type
self.assertEqual(expected, rc, result + report)
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 1 != 0 : Got exit code 0, expected 1
======================================================================
FAIL: test_sock_stream (__main__.ApparmorUnixDomainConnect.test_sock_stream)
Test mediation of file based SOCK_STREAM connect
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/ryan-lee/qrt-test-apparmor/./test-apparmor.py", line 3706, in
test_sock_stream
self._test_sock_type('stream')
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^
File "/home/ryan-lee/qrt-test-apparmor/./test-apparmor.py", line 3694, in
_test_sock_type
self.assertEqual(expected, rc, result + report)
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 1 != 0 : Got exit code 0, expected 1
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: John Johansen (jjohansen)
Status: New
** Affects: apparmor (Ubuntu Plucky)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Plucky)
Importance: Undecided
Assignee: John Johansen (jjohansen)
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Plucky)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Plucky)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103460
Title:
QRT AppArmorUnixDomainConnect test failures on Plucky 6.14 kernel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2103460/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
