Bugzilla – Full Text Bug Listing
| Summary: | eventConsumerJob in org.eclipse.epp.usagedata.internal.gathering.services.UsageDataService is never finished | ||
|---|---|---|---|
| Product: | [Technology] EPP | Reporter: | Snjezana Peco <snjezana.peco> |
| Component: | Usage Data Collector | Assignee: | Wayne Beaton <wayne.beaton> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | manderse, mknauer |
| Version: | unspecified | ||
| Target Milestone: | 1.3.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
Can you just exclude the UDC bundles from your test configuration? This seems like just as reasonable a solution as setting a system property... Or have I missed something? I am assuming that my suggestion to not include the UDC bundles provided the answer and am closing this as WONTFIX. Reopen if I've made an invalid assumption. |
Build Identifier: 20090920-1017 The UserDataService class creates eventConsumerJob that, by default, is running while running Eclipse. JBT PDE tests have to wait until all Eclipse jobs are finished (Eclipse builder, validators ...). The following method is used: public static void waitForIdle(long delay) { long start = System.currentTimeMillis(); while (!Job.getJobManager().isIdle()) { delay(delay); if ( (System.currentTimeMillis()-start) > MAX_IDLE ) throw new RuntimeException("A long running task detected"); //$NON-NLS-1$ } } Since eventConsumerJob is never finished, this method throws RuntimeException after MAX_IDLE seconds. It is not possible to stop monitoring without introducing a dependency to the org.eclipse.epp.usagedata.gathering plugin. I see two solutions to solve the problem : - creating eventConsumerJob so that it is started and finished periodically - the UsageDataCaptureActivator.start method would check for a system property (org.eclipse.epp.usagedata.gathering.disabled, for instance); if the property is true, the monitoring wouldn't be started. The tests could be started with the VM args -Dorg.eclipse.epp.usagedata.gathering.disabled=true This solution is easier to implement. A similar problem was existing in mylyn (https://bugs.eclipse.org/bugs/show_bug.cgi?id=198241) Reproducible: Always Steps to Reproduce: Job.getJobManager().isIdle() always returns false if org.eclipse.epp.usagedata.gathering is started.