Currently, if the users needs to run coverage, there is a pre-step before running it as explain in [1]. This is too intrusive for some users that do not have system privileges. Ideally, oe-selftest should instrument a LOCAL user site file before starting any tests. One possible way is to use [2], but there may be other ways to handle this. [1] https://coverage.readthedocs.org/en/coverage-4.0.2/subprocess.html [2] https://docs.python.org/2/library/site.html#site.USER_SITE
Fixed: http://lists.openembedded.org/pipermail/openembedded-core/2016-February/117622.html
it should be in progress review instead of resolved
v2: http://lists.openembedded.org/pipermail/openembedded-core/2016-February/117674.html
v3 http://lists.openembedded.org/pipermail/openembedded-core/2016-February/117794.html
Verified and Passed.
Created attachment 3023 [details] oe-selftest.log (In reply to comment #5) > Verified and Passed. I ran oe-selftest --run-tests bblayers.BitbakeLayers.test_bitbakelayers_flatten --coverage and everything passed. Poky commit: 3f7aa6fc5d018747e8d3bc8d6038215c36c9ef54 Attached you can find log.