[apparmor] [patch] inprove runtests-py*.sh

Christian Boltz apparmor at cboltz.de
Thu Jul 17 13:58:16 UTC 2014


Hello,

Am Mittwoch, 16. Juli 2014 schrieb Steve Beattie:
> On Wed, Jul 16, 2014 at 01:39:49PM +0200, Christian Boltz wrote:

> > I know "all tests succeeded" is the expected result, and we should
> > always have that.
> 
> Indeed. I wish I could get that with make check with the
> distribution's python apparmor packages installed on ubuntu 14.04,
> but thanks to some python brain-damage that causes it to always use
> the system version of libraries instead of the local ones (even with
> your patches to append ',.' to sys.path, as well as explicitly
> setting the PYTHONPATH variable), I can't.

Clean build system (chroot) anyone? ;-)

I can recommend OBS *eg* - it can even create *.deb packages ;-)

> > Nevertheless it's useful to be able to run all tests
> > even if the first one fails ;-)  (maybe I'm able to fix the second
> > one?)
> Eh, I can understand that. Fair warning though, I don't use these
> scripts for testing because the non test-*.py scripts always failed
> for me, and I hadn't gotten around to fixing them due to them looking
> like they had a bunch of issues to be resolved.

All *.py work fine here (with the exception of minitools_test.py because 
the profiles used for testing contain ptrace rules, and I still have 
apparmor_parser 2.8.x installed and no in-tree parser compiled).

Therefore it would be interesting to see what fails for you (after all 
my patches are in).


BTW: the minitools seem to always use the system parser. Should we add a 
way to specify the path to the parser (like a parser built in-tree)?


Regards,

Christian Boltz
-- 
[...] aber letzten Endes ist er mein Chef, und wenn er karierte
Maiglöckchen haben will, dann soll er sie kriegen, sofern ich
diese beschaffen kann. [Martin Mewes in suse-linux]




More information about the AppArmor mailing list