Bug 9930 - eo-selftest: add a coverage subcommand to handle coverage related tasks
Summary: eo-selftest: add a coverage subcommand to handle coverage related tasks
Status: RESOLVED DUPLICATE of bug 11582
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: Scripts and Tools (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 2.4
Assignee: Aníbal Limón
QA Contact: Humberto Ibarra
URL:
Whiteboard:
Depends on:
Blocks: 9931
  Show dependency tree
 
Reported: 2016-07-13 19:02 UTC by Humberto Ibarra
Modified: 2017-06-01 15:57 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Humberto Ibarra 2016-07-13 19:02:13 UTC 
coverage measurement is currently making the syntax and code of oe-selftest quite messy. If a coverage subcommand woudl exist to manipulate coverage settings outside of the run tasks then it would increase readability of commands and reduce confussion. It would also give a better control over the code.
Comment 1 Benjamin Esquivel 2016-11-03 22:12:58 UTC 
Re-assigning to Mariano since he has better visibility of what's going on with oe-selftest for the oeqa rewrite.
Comment 2 Leonardo Sandoval Gonzalez 2016-11-04 21:25:36 UTC 
(In reply to comment #1)
> Re-assigning to Mariano since he has better visibility of what's going on
> with oe-selftest for the oeqa rewrite.

This bug is just related to the argparse python code, and Humberto has more insight on this.
Comment 3 Benjamin Esquivel 2016-11-07 17:47:15 UTC 
We could reaassign it to Humberto but whatever he ends up doing, Mariano will re-write it. Your call Leo.
Comment 4 Leonardo Sandoval Gonzalez 2017-06-01 15:57:13 UTC 
bug 11582 is file against the new oe-qa framework / oe-selftest, so work on this one instead.

*** This bug has been marked as a duplicate of bug 11582 ***