Bugzilla – Full Text Bug Listing
| Summary: | Launching Junit plug-in test takes for ever | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Jay Arthanareeswaran <jarthana> | ||||
| Component: | UI | Assignee: | PDE-UI-Inbox <pde-ui-inbox> | ||||
| Status: | RESOLVED WORKSFORME | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | curtis.windatt.public, florian | ||||
| Version: | 3.7 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
What version of Eclipse are you using? This looks like a dupe of 335956, but we made improvements to it in late 3.7. This occurs with 3.8 M1 - build I20110803-1800. 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. (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. 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%? 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. |
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.