Community
Participate
Working Groups
1. Issue the following command: java -cp (Test framework path)/bin -agentlib:JPIBootLoader=JPIAgent:server=standalone;CGProf org.eclipse.tptp.scenario.thread.PowerWorkload 100 2. Verify the results: java -Dtrim.args=true -cp (Test framework path)\bin org.eclipse.tptp.ac.verification.Verifier -i all trace.trcxml The problem persists on Windows 2003 Server with SUN5, SUN6 and BEA JDK.
Additional verifier logs 1. agg_threadPowerWorkload_10 on win2003 ia32 SUN5 VERIFICATION ERROR: org.eclipse.tptp.ac.verification.TraceVerificationException: at 695: <methodDef name="interlockedIncCount" signature="()V" startLineNumber="45" endLineNumber="48" methodId="69587" classIdRef="288"/> RULE_M01: Method id must be unique for each method definition event. Existing method: id=69587,name=run.()V 2. threadPowerWorkload_10 on win2003 ia32 SUN5 VERIFICATION ERROR: org.eclipse.tptp.ac.verification.TraceVerificationException: at 71791: <methodDef name="dtoa" signature="(IJI)V" startLineNumber="0" endLineNumber="0" methodId="69625" classIdRef="294"/> RULE_M01: Method id must be unique for each method definition event. Existing method: id=69625,name=-init-.(D)V 3. threadMathWorkload 10 on win2003 ia32 SUN6 org.eclipse.tptp.ac.verification.TraceVerificationException: at 690: <methodDef name="" signature="" methodId="70050" classIdRef="0"/> RULE_C02: Class must be defined before being referenced. MethodDef: classID=0, methodID=70050, name=, sig=
(In reply to comment #1) These errors are caused by the same data corruption that crashes CGProf, as described in Bug 187006. Adding a dependency. Additionally, you may also get the following non-critical errors: WARNING: at 763: <methodDef name="getName" signature="()Ljava/lang/String;" startLineNumber="1013" endLineNumber="1013" methodId="65975" classIdRef="34"/> The same methodDef was traced for: classID=34, methodID=65975, java.lang.Thread.getName()Ljava/lang/String; These are related to Bug 168531 (multiple New Method events for the same method). The data loader can handler these multiple entries, therefore it is not critical. Adding a dependency on Bug 168531. Recommend to target to future.
If this Bugzilla is planed to be completed in 4.5, please add the plan keyword. Otherwise, please target to future. In addition, if this Bugzilla is committed to be completed in 4.5, please change the priority to P1.
I was unable to reproduce it within the last testing phase for 4.5i4. Closing this so far.
Reopening to be able reassign it to Stas
> I was unable to reproduce it within the last testing phase for 4.5i4. > Closing this so far. > Repeating.
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.
