Err, here are the results with the proper invocation of test-apparmor.py to get the parser stress tests too: $ sudo ./test-apparmor.py --with-parser-stress -v ... Run parser stress test ... Generating 1000 profiles... Loading directory of profiles into buffer cache
real 0m1.448s user 0m3.648s sys 0m0.580s Running preprocess only parser on directory of profiles real 4m21.596s user 4m19.216s sys 0m3.120s Running full parser on directory of profiles real 4m27.704s user 4m25.037s sys 0m3.676s Loading equivalent profile into buffer cache real 0m0.004s user 0m0.000s sys 0m0.004s Running preprocess only parser on single equiv profile real 4m29.743s user 4m29.469s sys 0m0.212s Running full parser on single equivalent profile real 4m39.586s user 4m39.321s sys 0m0.196s ok Run subdomain stress test ... (skipped: use --with-subdomain-stress to enable) ok Cleanup downloaded source ... ok ---------------------------------------------------------------------- Ran 25 tests in 1387.654s OK (FYI, the subdomain stress tests intentionally never complete which is why they aren't run. This may change in a future version of AppArmor). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/660077 Title: update AppArmor to 2.5.1 (for upstream and backported maverick kernels) -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
