Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 354338 - Launching Junit plug-in test takes for ever
Summary: Launching Junit plug-in test takes for ever
Status: RESOLVED WORKSFORME
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-10 03:55 EDT by Jay Arthanareeswaran CLA
Modified: 2015-12-18 03:54 EST (History)
2 users (show)

See Also:


Attachments
Thread dump (11.28 KB, text/plain)
2011-08-10 03:55 EDT, Jay Arthanareeswaran CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jay Arthanareeswaran CLA 2011-08-10 03:55:03 EDT
Created attachment 201212 [details]
Thread dump

The launch of a Junit tests seem to have hit a dead-lock. It's stuck at 57 % and says "Verifying launch attributes". This is not the first time I have seen this. However, usually it takes a while but the tests start running eventually. But now it's stuck there forever. Even restarting eclipse is not helping.

Attaching the thread dump for analysis.
Comment 1 Curtis Windatt CLA 2011-08-10 10:48:24 EDT
What version of Eclipse are you using?

This looks like a dupe of 335956, but we made improvements to it in late 3.7.
Comment 2 Jay Arthanareeswaran CLA 2011-08-10 10:54:06 EDT
This occurs with 3.8 M1 - build I20110803-1800.
Comment 3 Curtis Windatt CLA 2011-08-12 15:21:45 EDT
Taking a brief look at your thread dump, it looks like it was working at deleting the previous workspace.  Do your tests create a large workspace?  The file I/O might be your bottleneck.
Comment 4 Jay Arthanareeswaran CLA 2011-08-16 01:36:50 EDT
(In reply to comment #3)
> Taking a brief look at your thread dump, it looks like it was working at
> deleting the previous workspace.  Do your tests create a large workspace?  The
> file I/O might be your bottleneck.

Yes, they use a large workspace. Do you think deleting the test workspace manually before launching would help? Let me try that anyway and report back.
Comment 5 Jay Arthanareeswaran CLA 2011-08-16 02:27:26 EDT
With a clean test workspace, everything works alright. The workspace did have some  really large content. I think we can close this bug. A curious question, though, is, why do we often see the launch taking significant time at 57%?
Comment 6 Curtis Windatt CLA 2011-08-16 09:31:03 EDT
The progress reporting in the PDE launcher is very granular.  We start the task with too few ticks available.  Then, all of the methods we call to create the necessary arguments/configuration/etc. do not take progress monitors and they can take significant time.  We cannot easily add progress monitoring to those methods as our launch delegate is in a public package (API).

Thanks for reporting back.  Closing as WORKSFORME.

Perhaps there is a way to more efficiently delete the workspace directory.