test_caching_954469 in qrt_apparmor failed on Precise 3.13

Bug #1667648 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
QA Regression Testing
Fix Released
Undecided
Unassigned
ubuntu-kernel-tests
Fix Released
Undecided
Unassigned

Bug Description

After we move our test to the new server, I can see test_caching_954469 failed on Precise 3.13 amd64. (Or maybe this is a new test case?)

I didn't call this as a regression, since it passed on a laptop here.

Error log:
======================================================================
FAIL: test_caching_954469 (__main__.ApparmorTest)
Test recaching
----------------------------------------------------------------------
Traceback (most recent call last):
File "./test-apparmor.py", line 1284, 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' (1487927477.81 != 1487927481.88)

Full log:
http://pastebin.ubuntu.com/24058290/

Revision history for this message
Sean Feole (sfeole) wrote :

 very old bug, with no action on it, marking bug as incomplete and will close in 5 days if no update.

Changed in ubuntu-kernel-tests:
status: New → Incomplete
Changed in qa-regression-testing:
status: New → Incomplete
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Changed in qa-regression-testing:
status: Incomplete → Fix Released
Changed in ubuntu-kernel-tests:
status: Incomplete → Fix Released
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.