|
|
Re: How to detect what is causing excessive Autobuild [message #990375 is a reply to message #990276] |
Wed, 12 December 2012 08:31 |
Roland Tepp Messages: 36 Registered: July 2009 |
Member |
|
|
Thanks, that's exactly what I asked for :)
11.12.2012 18:51, Daniel Megert kirjutas:
> On 11.12.2012 12:36, Roland Tepp wrote:
>> Hi,
>>
>> Quite recently I started to notice that my eclipse started triggering
>> workspace build jobs excessively.
>>
>> Sometimes even having two or more "Building workspace" jobs in the queue.
>>
>> This has started to interfere quite heavily with my work, so I am
>> looking for a remedy.
> I can't provide a remedy but some tracing options that might allow you
> to see the culprit or at least file a bug report.
>
> # Turn on debugging for the org.eclipse.core.resources plugin.
> org.eclipse.core.resources/debug=true
>
> # Reports the start and end of all builder invocations
> org.eclipse.core.resources/build/invoking=true
>
> # Reports the start and end of build delta calculations
> org.eclipse.core.resources/build/delta=true
>
> # For incremental builds, displays which builder is being run and
> because of changes in which project.
> org.eclipse.core.resources/build/needbuild=true
>
> # Prints a stack trace every time an operation finishes that requires a
> build
> org.eclipse.core.resources/build/needbuildstack=true
>
> # Turn on debug tracing for org.eclipse.jdt.core plugin
> org.eclipse.jdt.core/debug=true
>
> # Reports incremental builder activity : nature of build, built state
> reading, indictment process
> org.eclipse.jdt.core/debug=true
> org.eclipse.jdt.core/debug/builder=true
> org.eclipse.jdt.core/debug/builder/stats= true
>
>
> See also
> http://wiki.eclipse.org/FAQ_How_do_I_use_the_platform_debug_tracing_facility%3F
>
>
> Dani
>>
>> My eclipse configuration is following:
>>
>> Eclipse SDK
>> Version: 3.8.1
>> Build id: M20120914-1540
>>
>> I have quite a few addons installed on top of this configuration.
>> I am sure one of these is the culprit but I am loathe to use
>> "uninstall everything" approach.
>>
>> I'd rather find out who is responsible for kicking off the excessive
>> workspace build jobs and report it if possible.
>>
>> Any way - does anybody here have a suggestion how to detect which
>> plugin, thread, process of service in my Eclipse is ordering the build
>> jobs?
>>
>>
>> - Roland
|
|
|
Re: How to detect what is causing excessive Autobuild [message #990563 is a reply to message #990375] |
Thu, 13 December 2012 08:21 |
Roland Tepp Messages: 36 Registered: July 2009 |
Member |
|
|
So, it seems that the culprit was a plugin calles AppXRay by Oracle that
came along with some Oracle's toolset bundle.
This did not come out of the provided logs exactly, but the logs
provided me with a que to look for the plug-in configuration and
suitable course of action (which was to disable the above mentioned
plug-in) followed from there.
Once disabled, the incessent builds stopped.
Thanks again for the hint.
12.12.2012 10:31, Roland Tepp kirjutas:
> Thanks, that's exactly what I asked for :)
>
> 11.12.2012 18:51, Daniel Megert kirjutas:
>> On 11.12.2012 12:36, Roland Tepp wrote:
>>> Hi,
>>>
>>> Quite recently I started to notice that my eclipse started triggering
>>> workspace build jobs excessively.
>>>
>>> Sometimes even having two or more "Building workspace" jobs in the
>>> queue.
>>>
>>> This has started to interfere quite heavily with my work, so I am
>>> looking for a remedy.
>> I can't provide a remedy but some tracing options that might allow you
>> to see the culprit or at least file a bug report.
>>
>> # Turn on debugging for the org.eclipse.core.resources plugin.
>> org.eclipse.core.resources/debug=true
>>
>> # Reports the start and end of all builder invocations
>> org.eclipse.core.resources/build/invoking=true
>>
>> # Reports the start and end of build delta calculations
>> org.eclipse.core.resources/build/delta=true
>>
>> # For incremental builds, displays which builder is being run and
>> because of changes in which project.
>> org.eclipse.core.resources/build/needbuild=true
>>
>> # Prints a stack trace every time an operation finishes that requires a
>> build
>> org.eclipse.core.resources/build/needbuildstack=true
>>
>> # Turn on debug tracing for org.eclipse.jdt.core plugin
>> org.eclipse.jdt.core/debug=true
>>
>> # Reports incremental builder activity : nature of build, built state
>> reading, indictment process
>> org.eclipse.jdt.core/debug=true
>> org.eclipse.jdt.core/debug/builder=true
>> org.eclipse.jdt.core/debug/builder/stats= true
>>
>>
>> See also
>> http://wiki.eclipse.org/FAQ_How_do_I_use_the_platform_debug_tracing_facility%3F
>>
>>
>>
>> Dani
>>>
>>> My eclipse configuration is following:
>>>
>>> Eclipse SDK
>>> Version: 3.8.1
>>> Build id: M20120914-1540
>>>
>>> I have quite a few addons installed on top of this configuration.
>>> I am sure one of these is the culprit but I am loathe to use
>>> "uninstall everything" approach.
>>>
>>> I'd rather find out who is responsible for kicking off the excessive
>>> workspace build jobs and report it if possible.
>>>
>>> Any way - does anybody here have a suggestion how to detect which
>>> plugin, thread, process of service in my Eclipse is ordering the build
>>> jobs?
>>>
>>>
>>> - Roland
>
|
|
|
Powered by
FUDForum. Page generated in 0.02901 seconds