Comment 1 Kendric Wang 2008-05-06 17:59:05 EDT

The following AGR testsuites have been updated and checked in during i7:

Platform.Execution.LaunchConfig.JVMTI
Platform.Execution.ProbeKit.JVMTI.<Win_IA32, EM64T, Linux_IA32>
Platform.Execution.ProbekitBCI.<Win_IA32, Linux_IA32>

For the remote testsuites, I re-added the "Everything", "MultipleProbes", and "ClassPath" testcases back into the behaviour.

Comment 2 jkubasta 2008-05-14 11:29:46 EDT

Kendric, will the final case be updated in i8?

Comment 3 jkubasta 2008-07-16 11:37:20 EDT

Tony, would you please investigate in August (i.e once your development work is done). Thanks.

Comment 4 Tony Wang 2008-08-29 10:56:47 EDT

I tried to run those tests during 4.5.1 TP1, and here are the updated results:

1. Platform.Execution.LaunchConfig.JVMTI
   Works well, no failed verdict

2. Platform.Execution.ProbeKit.JVMTI.<Win_IA32, EM64T, Linux_IA32>
   Platform.Execution.ProbekitBCI.<Win_IA32, Linux_IA32>
 1)Win_IA32
   Works well, have the same failed cases as the old execution file

 2)EM64T
   Works well like Win_IA32, usually have one failed test case(unstable, 2 or more some times, but they are failed by the same reason(error))

 3)Linux_IA32
   For some command macro, the linux one are using different id compare with windows one, since they are sharing the same test case, the solution could be trying to find a way to meet the needs of all machine...or separate the tests by different machines.

Comment 5 Paul Slauenwhite 2008-11-03 11:18:15 EST

Joanna, can you assign this defect to an active member of the Platform Project?

Comment 6 Paul Slauenwhite 2008-11-03 11:57:38 EST

Increasing the severity since blocking the 4.5.2 I1 TP.

Comment 7 Raheel Ashraf 2008-11-19 12:09:30 EST

The catch test case is failing because of bug#236359

Comment 8 Raheel Ashraf 2008-11-19 12:11:29 EST

*** Bug 192730 has been marked as a duplicate of this bug. ***

Comment 9 jkubasta 2008-11-19 15:07:10 EST

*** Bug 187064 has been marked as a duplicate of this bug. ***

Comment 10 Kathy Chan 2009-05-12 17:40:06 EDT

Retargeting to v4.6.1.  This defect depends on bug 236359.

Comment 11 Kathy Chan 2009-08-07 10:36:14 EDT

Retargeting to future since the bugs it depends on are targeted for future as well.

Comment 12 Paul Slauenwhite 2009-09-24 15:16:13 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 13 Paul Slauenwhite 2009-09-24 15:22:45 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.