Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 64540

Summary:	Auto build interrupted and not resumed
Product:	[Eclipse Project] Platform	Reporter:	Tod Creasey <Tod_Creasey>
Component:	Resources	Assignee:	Platform-Resources-Inbox <platform-resources-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	critical
Priority:	P1	CC:	dirk_baeumer, john.arthorne
Version:	3.0
Target Milestone:	3.0 RC1
Hardware:	PC
OS:	Windows XP
Whiteboard:
Bug Depends on:
Bug Blocks:	63635, 64546

Description Tod Creasey

2004-05-28 09:06:27 EDT

20040528 (although I saw it on 20040527)

Auto build appears to run everytime I launch something after a clean for the 
first couple of times. This is a real hassle as lauching fails frequently as a 
result of this extra builds.

STEPS
1) Load platform-ui from HEAD and org.eclipse.ui.tests from HEAD
2) Clean them.
3) Wait for the build to finish
4) Try and run UITestSuite. You will get a Launch failed notification and two 
builds will happen

Comment 1 John Arthorne

2004-05-28 12:39:54 EDT

*** Bug 64543 has been marked as a duplicate of this bug. ***

Comment 2 Tod Creasey

2004-05-28 14:25:32 EDT

Looking at the progress monitor to looks like there is a build going on 
whether you want to it to or not when launching - we get compiler progress 
even though the auto build is off.

Comment 3 Tod Creasey

2004-05-28 15:42:37 EDT

We found a case where it is creating a few more markers each time and then 
stopping. A clean then a manual build all fixed it

STEPS
1) Load ui, workbench, views, ide, jface and ui.tests out of HEAD
2) 4 items showed up.
3) clean
4) Got up to 17
5) Turn off autobuild
6) Build All
7) 337 (the correct number) showed up

John thinks this may be due to autobuilds being cancelled.

Comment 4 John Arthorne

2004-05-28 17:13:08 EDT

*** Bug 64546 has been marked as a duplicate of this bug. ***

Comment 5 John Arthorne

2004-05-28 17:15:16 EDT

*** Bug 64559 has been marked as a duplicate of this bug. ***

Comment 6 John Arthorne

2004-05-28 17:20:30 EDT

Autobuild was being interrupted by other background jobs (periodic resource
change notification). Normally the job that interrupts the autobuild will kick
off another autobuild when it completes. We made a change two days ago (fix for
bug 63322), to allow jobs with no rule to run concurrently with autobuild. This
means it was possible for a job to interrupt autobuild, but then complete before
the autobuild responds to the interruption. Thus, no job would be around to
start the build again.

The key to reproducing the problem is to cause an autobuild to occur that needs
to build multiple projects. The build will be interrupted after building one
project, and will not resume to build the rest.