Bug 519776 - [builder] Potential infinite build loop in builder due to Synchronizer.setSyncInfo
Summary: [builder] Potential infinite build loop in builder due to Synchronizer.setSyn...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.8.2   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-17 13:19 EDT by Sebastian Zarnekow CLA
Modified: 2020-02-17 18:19 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian Zarnekow CLA 2017-07-17 13:19:32 EDT 
Synchronizer#setSyncInfo calls prepareOperation with a resource. The resource is in conflict with the build rule thus prepareOperation will cancel the auto build.

This happens especially in the context of Xtext builders, which generate code, and SVN directories, that are monitored by Subclipse.
Comment 1 Eclipse Genie CLA 2017-07-17 14:20:47 EDT 
New Gerrit change created: https://git.eclipse.org/r/101379
Comment 2 Sebastian Zarnekow CLA 2017-07-19 04:58:55 EDT 
Could someone please take a look at this changeset?
Comment 3 Andrey Loskutov CLA 2017-07-19 09:37:52 EDT 
I assume the problem is not introduced in 4.8, so I'm changing the version to 3.8.2. Feel free to change to the first version where you observe the problem.
Comment 4 Sebastian Zarnekow CLA 2017-07-19 09:44:24 EDT 
(In reply to Andrey Loskutov from comment #3)
> I assume the problem is not introduced in 4.8, so I'm changing the version
> to 3.8.2. Feel free to change to the first version where you observe the
> problem.

Thank you, I'm bad at housekeeping :)
Comment 5 Eclipse Genie CLA 2020-02-17 18:19:59 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.