Bug 206637

Summary:	[Build] builder infrastructure should protect itself from endless interruptions
Product:	[Eclipse Project] Platform	Reporter:	Markus Keller <markus.kell.r>
Component:	Resources	Assignee:	Platform-Resources-Inbox <platform-resources-inbox>
Status:	NEW ---	QA Contact:
Severity:	major
Priority:	P3	CC:	daniel_megert, eclipse.sprigogin, jamesblackburn+eclipse, jkubitz-eclipse, kent_johnson, Lars.Vogel, rgrunber
Version:	3.4
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:
Bug Depends on:
Bug Blocks:	89301

Description Markus Keller

2007-10-17 11:35:12 EDT

I20071016-1215

The builder infrastructure should protect itself from misbehaving scheduling rules that cause interruptible builders to loop endlessly (e.g. the one from bug 203058 comment 6 to 9). It could e.g. only accept at most 5 repeated interruptions from the same scheduling rule and then log a warning and discard further interruptions until a build has finished.

Bug 203058 comment 10 and bug 89301 comment 20 indicate that builder implementors don't want to make use of IncrementalProjectBuilder#isInterrupted() because of this problem.

Comment 1 Markus Keller

2008-12-04 12:25:55 EST

This bug is blocking JDT/Core from using IncrementalProjectBuilder.isInterrupted() because they fear that broken third-party plugins could shed a bad light on the Java builder.

Comment 2 Eclipse Genie

2019-12-13 18:41:49 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.

If you have further information on the current state of the bug, please add it. 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.

Comment 3 Dani Megert

2019-12-17 05:04:54 EST

Nothing has been done yet.

Comment 4 Lars Vogel

2020-08-12 06:29:07 EDT

(In reply to Markus Keller from comment #1)
> This bug is blocking JDT/Core from using
> IncrementalProjectBuilder.isInterrupted() because they fear that broken
> third-party plugins could shed a bad light on the Java builder.

Roland, do you know if there is already a feature request for this in JDT core?

Comment 5 Rolf Theunissen

2020-08-12 07:32:25 EDT

(In reply to Lars Vogel from comment #4)
> (In reply to Markus Keller from comment #1)
> > This bug is blocking JDT/Core from using
> > IncrementalProjectBuilder.isInterrupted() because they fear that broken
> > third-party plugins could shed a bad light on the Java builder.
> 
> Roland, do you know if there is already a feature request for this in JDT
> core?

I think you mean a different 'Roland'.

Comment 6 Lars Vogel

2020-08-12 07:57:53 EDT

(In reply to Rolf Theunissen from comment #5)
> I think you mean a different 'Roland'.

Roland Grunberg, which I also cc'ed to the bug.

Comment 7 Lars Vogel

2021-04-01 05:07:26 EDT

(In reply to Markus Keller from comment #1)
> This bug is blocking JDT/Core from using
> IncrementalProjectBuilder.isInterrupted() because they fear that broken
> third-party plugins could shed a bad light on the Java builder.

This would result in a much faster user flow in JDT, currently the user actions are blocked during a JDT build.