Bug 519776

Summary:	[builder] Potential infinite build loop in builder due to Synchronizer.setSyncInfo
Product:	[Eclipse Project] Platform	Reporter:	Sebastian Zarnekow <sebastian.zarnekow>
Component:	Resources	Assignee:	Platform-Resources-Inbox <platform-resources-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	loskutov
Version:	3.8.2
Target Milestone:	---
Hardware:	All
OS:	All
See Also:	https://git.eclipse.org/r/101379 https://bugs.eclipse.org/bugs/show_bug.cgi?id=486083 https://bugs.eclipse.org/bugs/show_bug.cgi?id=517725 https://bugs.eclipse.org/bugs/show_bug.cgi?id=478634
Whiteboard:	stalebug

Description Sebastian Zarnekow

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

2017-07-17 14:20:47 EDT

New Gerrit change created: https://git.eclipse.org/r/101379

Comment 2 Sebastian Zarnekow

2017-07-19 04:58:55 EDT

Could someone please take a look at this changeset?

Comment 3 Andrey Loskutov

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

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

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.