AppArmor

AppArmor tests fail on Precise i386

Bug #1534165 reported by Brad Figg on 2016-01-14

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	AppArmor	New	Undecided	Unassigned

Bug Description

This test is failing consistently on 5 different systems.

FAIL: test_caching_954469 (__main__.ApparmorTest)
  Test recaching
  ----------------------------------------------------------------------
  Traceback (most recent call last):
    File "./test-apparmor.py", line 1278, in test_caching_954469
      self.assertEquals(orig[c].st_mtime, current[c].st_mtime, "Modification times do not match for '%s' (%s != %s)" % (c, orig[c].st_mtime, current[c].st_mtime))
  AssertionError: Modification times do not match for '/etc/apparmor.d/cache/bin.ping' (1452727547.49 != 1452727552.58)

Tags:

Revision history for this message

Seth Arnold (seth-arnold) wrote on 2016-01-20:

cache_syscalls Edit (125.4 KiB, text/plain)

I'm trying out sysdig on this; of course we can't get this issue to reproduce on our systems which is a serious annoyance, but here's a sysdig trace captured while running:

python -m unittest test-apparmor.ApparmorTest.test_caching_954469

The trace was generated with:
sysdig -w out
sysdig -r out > syscalls
fgrep /cache/ syscalls > cache_syscalls

(This was generated with the sysdig upstream packages and the curl .. | sudo bash installer. Pity our autopkgtest hosts can't just do the same to grab this kind of trace...)

Christian Boltz (cboltz) on 2016-10-13

tags:

added: aa-parser