Bug 8930

Summary: oe-selftest: coverage should work without instrumenting system sitecustomize.py file
Product: [QA/Testing] Build Testing Reporter: Leonardo Sandoval Gonzalez <leonardo.sandoval.gonzalez>
Component: generalAssignee: Humberto Ibarra <humberto.ibarra.lopez>
Status: VERIFIED FIXED QA Contact: Francisco Pedraza <francisco.j.pedraza.gonzalez>
Severity: normal    
Priority: Medium+ CC: alexandru.c.georgescu, benjamin.esquivel, eduard.bartosh, humberto.ibarra.lopez
Version: 2.0   
Target Milestone: 2.1 M3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
oe-selftest.log none

Description Leonardo Sandoval Gonzalez 2016-01-14 23:05:53 UTC 
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
Comment 2 Leonardo Sandoval Gonzalez 2016-02-16 20:33:30 UTC 
it should be in progress review instead of resolved
Comment 5 Francisco Pedraza 2016-03-10 18:40:27 UTC 
Verified and Passed.
Comment 6 Francisco Pedraza 2016-03-10 19:52:14 UTC 
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.