Marking bug as invalid for AppArmor (Ubuntu) because the bug is solely
in the AppArmor kernel side.

** Changed in: apparmor (Ubuntu Plucky)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2103460

Title:
  QRT AppArmorUnixDomainConnect test failures on Plucky 6.14 kernel

Status in apparmor package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in apparmor source package in Plucky:
  Invalid
Status in linux source package in Plucky:
  Fix Released

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2103460/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to