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

Bug 200436

Summary:	Cumulative CPU Times too high on Linux IPF for tiagent
Product:	z_Archived	Reporter:	Kendric Wang <kendricw>
Component:	TPTP	Assignee:	jkubasta
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P2	CC:	analexee, guru.nagarajan, haggarty, jkubasta, paulslau
Version:	unspecified	Keywords:	plan
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	housecleaned460 closed460

Description Kendric Wang

2007-08-17 18:02:27 EDT

Build ID: I20070625-1500

Steps To Reproduce:
1. Start the workbench on WindowsXP and AC on tptpia64 (IPF).
2. Create a new external java application profile for CpuTime.
3. Specify 'tptpia64' as the host and 'CpuTime' as the Class name. (It can be found in
/org.eclipse.tptp.ac.testautomation/automation-files/external_classes/). In the Monitoring tab, select 'Execution Time Analysis'. Make sure 'Collect Method CPU time information' option is checked off for that profile type.
4. Launch CpuTime for profiling and wait for it to terminate.
5. Open "Execution statistics", select "Method statistics", and add the "Cumulative CPU time" column.

The expected Cumulative CPU times for MethodA and MethodB ought to be between 0.6s and 2.0s. The values that I get are around 4s, which are too high.


Setup Information:
Local Machine (WinXP)
- Eclipse 3.3.0
- EMF 2.2.24
- Java142

Test Machine (IPF - tptpia64)
- TPTP-4.4.0.2-200708010100 build for AC
- Sun JRE 1.5.0 (build 1.5.0_04-b05) for 64-bit machine
*IBM does not have jre150 available for IPF

Comment 1 Stanislav Polevic

2008-04-09 09:40:54 EDT

Reassigning to Igor.

Comment 2 jkubasta

2008-05-23 08:57:20 EDT

Deferral to future with PMC approval

Comment 3 Kathy Chan

2009-02-23 13:41:22 EST

Mass update of P1 enhancements and defects targetted to future to P2.

Comment 4 Paul Slauenwhite

2009-06-30 10:47:21 EDT

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant 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 defect is resolved as WONTFIX by the Project Lead since the originator of this defect has an inactive Bugzilla account and it may be no longer relevant. If this defect is still relevant and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.

Comment 5 Paul Slauenwhite

2009-06-30 10:48:06 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 the originator of this enhancement/defect has an inactive Bugzilla account 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.