Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 75283

Summary:	methodCount fragments should be handled
Product:	z_Archived	Reporter:	Sylvain Duguet <sylvain.duguet>
Component:	Hyades	Assignee:	Marius Slavescu <slavescu>
Status:	CLOSED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	closed460

Description Sylvain Duguet

2004-09-29 10:11:56 EDT

This is related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=75266 (Method 
Coverage only optimization).

<methodCount> fragments are emitted by piAgent but not handled by the model 
loader.

Looks like getting twice this kind of fragment with the same methodIdRef during 
the same process is not possible, because it is emitted at the end of the JVM 
process and that no snapshot mechanism currently exists that could cause this 
situation if called more than once.
So, it is my comprehension (but needs to be confirmed) that method count are not 
to be cumulated by the model loader, just replaced.
Of course, this enhancement should be compatible with the current set method for 
the calls attribute: it is computed from the method invocations.
There are two situations to be taken into account: with and without method 
invocations.

Do not hesitate to confirm or infirm the affirmations above!

Comment 1 Curtis d'Entremont

2004-11-10 11:36:54 EST

Were you still planning to support methodCount in addition to methodInvocations?

Comment 2 Sylvain Duguet

2004-11-10 12:22:12 EST

As https://bugs.eclipse.org/bugs/show_bug.cgi?id=75266 has been targeted to 
future, my priority for this is lower.
When I'm talking about compatibility with the method invocations, I'm just 
warning about the fact that counts must not be doubled, due to taking them into 
account while loading method invocations and also while loading methodCount that 
arrive at the end. It was just a reminder.

Comment 3 Harm Sluiman

2004-11-16 14:29:54 EST

update based on requirements group review

Comment 4 Marius Slavescu

2004-11-23 09:24:01 EST

Fix in CVS.

Comment 5 Paul Slauenwhite

2009-06-30 12:38:12 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.