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

Bug 106887

Summary: Execution harness blocks when there is a previous job hanging
Product: z_Archived Reporter: amehrega
Component: TPTPAssignee: Scott E. Schneider <scott.schneider>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description amehrega CLA 2005-08-12 14:45:49 EDT 
Based on my experience with the test execution harness it seems that it doesn't
treat each launch as a separate job.  If there is already a launched item being
processed, then successive launched items are blocked until the first one completes.

I think treating each launch as an asynchronous job is a better approach than
the current approach.  This especially makes a big difference when you're
building on top of the TPTP test framework.

With the current approach if a Junit doesn't halt, then it will hang the Junit
runner and not allow the user to launch successive JUnits or any other TPTP
tests.  To test this, create a JUnit with a test method that never halts, run
the Junit, and then create and run a manual test suite (the manual test suite
will get hanged at 50% because the test execution harness is probably waiting
for the Junit to finish)
Comment 1 Scott E. Schneider CLA 2005-09-06 10:50:11 EDT 
Please re-assign to me, thanks.
Comment 2 Scott E. Schneider CLA 2005-09-06 21:45:58 EDT 
There is a defect that already covers "reliable concurrent test execution."  --
closing this one as a duplicate defect.

*** This bug has been marked as a duplicate of 106852 ***
Comment 3 Scott E. Schneider CLA 2005-10-25 13:45:58 EDT 
Closed.