Bugzilla – Full Text Bug Listing
| Summary: | allow junit test suite of current context to run with low process priority | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Mik Kersten <mik.kersten> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P5 | CC: | darin.eclipse, mlists |
| Version: | 0.4 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | other | ||
| Whiteboard: | |||
|
Description
Mik Kersten
I see your point, however Java doesn't provide API to change/set the process priority nor does the VM allow to set it. Moving to Debug since they own launching (which JUnit reuses) however I don't see how to address this without providing platform specific natives. I agree it would be nice, but Java does not provide a way to set a priority on a spawned OS process. Currently no plans to write the platform specific natives. Moving to Mylar, which now has a custom JUnit launch configuration that dynamically creates a suite from your current task context. It's nice to be able to run that frequently, but annoying when it stops you from being able to type ;) *** Bug 118692 has been marked as a duplicate of this bug. *** Consideragbly less of an issue with dual-core machines, but we should still leave this on the table. Some of the API listed here could be helpful: bug 109211 gets my vote as I am running into similar issues. However, I would suggest to make this generic, i.e. for any launch configuration. This should not be restricted to Mylyn or unit tests. The reason is that we often debug software with the JDT that runs some heavy-duty analyses. If I do not reduce the priority and debug on my laptop, it more or less freezes for a minute or so. Right now I always set the priority manually in the process explorer but having an option in eclipse would be way better. In terms of implementation, could that here help? http://jakarta.apache.org/commons/sandbox/exec/ While it would be helpful to Mylyn users, this isn't a Mylyn specific requests and without it being contributed by the community we will not be looking at it in the 3.0 cycle. If someone is interested in a contribution it should probably go to Debug. A good starting point is the work that David Saff did for continuous testing. http://svn.csail.mit.edu/continuoustesting/ct-eclipse/org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/launcher/JUnitBaseLaunchConfiguration.java Darin: are you interested in having this moved over to Debug? The work on exec looks interesting, but it looks like it does not exist yet. I would mark this bug as "won't fix" until the support exists (I agree it should be a generic feature in debug/launching). However, I was interested to see the support in 1.5 to retrieve the system environment from ProcessBuilder. We have platform specific code to generate environment variables. If we ever migrate the debug platform to 1.5, we will be able to get rid of our platform specific code :-) Thanks Darin, makes sense. However, I'd like to keep this bug open to indicate that there is a need for it and to encourage voting if there is additional interest, so we can keep it on the Mylyn side for now. I don't think there is any need for this anymore. Please reopen if you disagree. |