[xenial] autopkgtest regression

Bug #1510362 reported by Martin Pitt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

On Xenial, linux' autopkgtests now consistently fail (http://autopkgtest.ubuntu.com/packages/l/linux/xenial/i386/):

======================================================================
  FAIL: test_easyprof (__main__.ApparmorTest)
  Test aa-easyprof
  ----------------------------------------------------------------------
  Traceback (most recent call last):
    File "./test-apparmor.py", line 1190, in test_easyprof
      self.assertEquals(expected, rc, result + report)
  AssertionError: Got exit code 127, expected 0
  [Errno 2] No such file or directory

  ======================================================================
  FAIL: test_python (__main__.ApparmorBindings)
  Test python binding
  ----------------------------------------------------------------------
  Traceback (most recent call last):
    File "./test-apparmor.py", line 2403, in test_python
      self.assertEquals(expected, rc, result + report)
  AssertionError: Got exit code 1, expected 0
  Traceback (most recent call last):
    File "/tmp/testlibZ6TSPQ/test-script", line 20, in <module>
      import LibAppArmor
  ImportError: No module named LibAppArmor

This could just be a missing test dependency (easyprof/the lib), or maybe also related to the "switch to Python 3.5 by default" transition in xenial-proposed.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1510362

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Martin Pitt (pitti)
tags: added: bot-stop-nagging
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

I think this may just need a no change rebuild for apparmor so that python 3.5 bindings are built.

Changed in linux (Ubuntu):
assignee: nobody → Jamie Strandboge (jdstrand)
Revision history for this message
Martin Pitt (pitti) wrote :

> I think this may just need a no change rebuild for apparmor so that python 3.5 bindings are built.

This was already done in wily; python3-libapparmor_2.10-0ubuntu6_amd64.deb does contain LibAppArmor/_LibAppArmor.cpython-35m-x86_64-linux-gnu.so .

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

I'm unable to reproduce this. I can say that a lot of tests fail due to bug #1511439. If I use 'sudo aa-disable /etc/apparmor.d/usr.bin.webbrowser-app' I can work around this.

$ sudo ./test-apparmor.py
...
test_easyprof (__main__.ApparmorTest)
Test aa-easyprof ... ok
...
test_python (__main__.ApparmorBindings)
Test python binding ...
  python
  python3
ok
...

If I remove python3-libapparmor (which also remove apparmor-easyprof), I see the same issue:
...

======================================================================
FAIL: test_easyprof (__main__.ApparmorTest)
Test aa-easyprof
----------------------------------------------------------------------
Traceback (most recent call last):
  File "./test-apparmor.py", line 1190, in test_easyprof
    self.assertEquals(expected, rc, result + report)
AssertionError: Got exit code 127, expected 0
[Errno 2] No such file or directory

======================================================================
FAIL: test_python (__main__.ApparmorBindings)
Test python binding
----------------------------------------------------------------------
Traceback (most recent call last):
  File "./test-apparmor.py", line 2403, in test_python
    self.assertEquals(expected, rc, result + report)
AssertionError: Got exit code 1, expected 0
Traceback (most recent call last):
  File "/tmp/testlib707vau/test-script", line 20, in <module>
    import LibAppArmor
ImportError: No module named 'LibAppArmor'

It seems the kernel's team scripts aren't pulling in 'apparmor-easyprof'.

$ sudo apt-get install apparmor-easyprof
...
$ sudo ./test-apparmor.py
...
test_easyprof (__main__.ApparmorTest)
Test aa-easyprof ... ok
...
test_python (__main__.ApparmorBindings)
Test python binding ...
  python
  python3
ok
...

Changed in linux (Ubuntu):
assignee: Jamie Strandboge (jdstrand) → nobody
status: Confirmed → Triaged
Revision history for this message
Brad Figg (brad-figg) wrote :

This is due to series specific information encoded into the kernel testing infrastructure. I've updated the infrastructure for Xenial.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Closing as per comment #5

Changed in linux (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.