Bug 164178 - The workbench launched by a JUnit plug-in takes a while to quit
Summary: The workbench launched by a JUnit plug-in takes a while to quit
Status: CLOSED WORKSFORME
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: TPTP (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P1 major (vote)
Target Milestone: ---   Edit
Assignee: Joe Toomey CLA
QA Contact:
URL:
Whiteboard:
Keywords: plan
Depends on:
Blocks:
 
Reported: 2006-11-10 16:07 EST by amehrega CLA
Modified: 2016-05-05 10:36 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description amehrega CLA 2006-11-10 16:07:24 EST 
I have a JUnit plug-in test suite under test-results/platform/org.eclipse.hyades.trace.ui.tests/plugin-junit/PDCoreUtilTester.testsuite that only has one test case.  When I launch the test suite, the second workbench that comes up takes about 1-2 min until it quits.

PDE Junit takes only a few seconds before the workbench exits (2-3 seconds).
Comment 1 Paul Slauenwhite CLA 2006-11-13 11:27:14 EST 
Since this defect does not restrict the execution of a TPTP JUnit plug-in test (albeit an important performance/usability issue), please defer to 4.4 and adjust the priority accordingly.
Comment 2 Julien Canches CLA 2006-11-14 04:45:31 EST 
Ali, are you using the default deployment?
Comment 3 amehrega CLA 2006-11-14 10:03:50 EST 
(In reply to comment #2)
> Ali, are you using the default deployment?

yes, I am.
Comment 4 Paul Slauenwhite CLA 2007-01-16 10:26:09 EST 
Reassigning to the component leads to triage for 4.4.
Comment 5 Paul Slauenwhite CLA 2007-01-17 09:44:06 EST 
Has the priority for this defect been recently reviewed given its severity?  If not, please take a few minutes and reevaluate the priority.
Comment 6 Joe Toomey CLA 2007-01-18 08:39:11 EST 
Is this a function of TPTP JUnit plugin tests, or of the test in question?  I have not observed this in running other JUnit plugin tests.  If the latter, I suggest we decrease the severity.
Comment 7 amehrega CLA 2007-01-18 11:28:38 EST 
I think we still need to investigate why this testsuite is taking an unusually long time to execute.  It could be a common problem that many users fall in.
Comment 8 Paul Slauenwhite CLA 2007-01-26 10:21:01 EST 
Increasing the priority to P1 since including in the 4.4 plan.
Comment 9 Paul Slauenwhite CLA 2007-01-26 10:21:24 EST 
Increasing the priority to P1 since including in the 4.4 plan.
Comment 10 Paul Slauenwhite CLA 2007-03-23 16:13:24 EDT 
Assigning target.
Comment 11 Paul Slauenwhite CLA 2007-05-18 16:18:32 EDT 
This defect is a candidate for deferral from the 4.4 release.  If the originator has opposition, please provide an argument against this deferral.
Comment 12 Paul Slauenwhite CLA 2007-05-28 15:09:25 EDT 
Assigning to i4 since i3 is complete but this defect belongs to a block of in-plan 4.4 defects that are candidates for deferral.
Comment 13 Joe Toomey CLA 2007-05-30 09:25:45 EDT 
I am unable to reproduce this problem.  Perhaps it was fixed by another code change.  When I run the PDCoreUtilTester test (with the 4.4 i3 RC using full AC with IBM 1.5 JRE), it completes within a few seconds of being launched.

Ali, can you please confirm that the problem is fixed?  If not, please reopen, and we can try to see what's different between our environments.
Comment 14 amehrega CLA 2007-05-30 10:51:23 EDT 
I wasn't able to reproduce the error in TPTP-4.4.0-200705220100
Thanks.
Comment 15 Joe Toomey CLA 2007-05-30 14:49:53 EDT 
Cool, thanks.

Closing.