Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 75266 - (Plat) Reduce footprint of collecting method coverage only with piAgent
Summary: (Plat) Reduce footprint of collecting method coverage only with piAgent
Status: CLOSED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: TPTP (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Bob Duncan CLA
QA Contact:
URL:
Whiteboard: closed460
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-29 08:08 EDT by Sylvain Duguet CLA
Modified: 2016-05-05 11:20 EDT (History)
2 users (show)

See Also:

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 Sylvain Duguet CLA 2004-09-29 08:08:06 EDT 
No need to collect all method invocations, count summary fragments are enough.
Currently, the attributes used for Method Coverage profiling are:
            <attribute
                  name="TRACE_MODE"
                  type="SETOPTION"
                  value="noObjectCorrelation">
            </attribute>
            <attribute
                  name="TICKET"
                  type="SETOPTION"
                  value="true">
            </attribute>
            <attribute
                  name="STACK_INFORMATION"
                  type="SETOPTION"
                  value="normal">
            </attribute>
            <attribute
                  name="METHOD_COUNTS"
                  type="SETOPTION"
                  value="true">
            </attribute>
If a subset exists avoiding collection of method invocations, it would reduce 
the quantity of information that is needed when gathering for Method Coverage 
only.
If it does not exist yet, it would be fine to allow it on piAgent side.

Fragments like <methodCount methodIdRef="7328" count="1"/> are enough with 
methodDef and classDef. methodEntry and methodExit are useless.

Note that methodCount would need to be handled by the model loader. This is not 
the case currently: they are ignored.
Comment 1 Marius Slavescu CLA 2004-09-29 09:45:45 EDT 
Sylvain, please open another feature for the "methodCount" loader, also provide
the fragment definition (schema).
Should the loader cumulate or replace the data at method level (calls attribute).
Comment 2 Sylvain Duguet CLA 2004-09-29 10:13:32 EDT 
Created https://bugs.eclipse.org/bugs/show_bug.cgi?id=75283 to reflect the model 
loader side of this enhancement.
Comment 3 Robert Danek CLA 2005-03-03 13:11:51 EST 
piAgent will send back methodCounts fragments when they are requested by the UI
 -- see bug 87094.
Comment 4 Curtis d'Entremont CLA 2005-03-08 14:07:00 EST 
IMPORTANT: This feature and bug 87094 must be committed together.
Comment 5 Bob Duncan CLA 2005-07-20 09:49:13 EDT 
Version/target housekeeping: enhancements that are targetted for "future" must 
record the version as "future" and the target as"---".
Comment 6 jkubasta CLA 2007-10-11 10:37:44 EDT 
No plans to implement
Comment 7 Paul Slauenwhite CLA 2007-12-19 07:58:41 EST 
Please change the target to the 4.5 iteration when this Bugzilla was resolved.
Comment 8 Paul Slauenwhite CLA 2009-06-30 13:22:29 EDT 
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.