Closed Bug 287905 Opened 20 years ago Closed 15 years ago

Abort current build if it's not building a change when there is a checkin

Categories

(Webtools Graveyard :: Tinderbox, enhancement)

Product:
Webtools Graveyard
Component:
Tinderbox
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: MatsPalmgren_bugz, Assigned: mcafee)

Details

It would be nice if ongoing builds without a "C" are restarted when there is a new checkin available. This will cut down the time one has to wait for a result of a checkin. If a "CVS storm" is a problem - could we at least have this for the fastest "Dep" boxes on each of the three primary platforms?
This is really only going to help where we have a slow build, and we should maybe add a pref to enable it there. If we detect a no-op build, we probably want to continue the tests part of the tbox loop for the performance machines, and we'll still wait around for the minimum time to avoid tbox reporting storms.
QA Contact: timeless → tinderbox
No-op builds are pretty much gone, so this isn't a problem any more.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.