Closed
Bug 617259
Opened 14 years ago
Closed 14 years ago
Optimize build prioritization
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: catlee, Assigned: catlee)
Details
(Whiteboard: [buildbot][simple])
Attachments
(1 file)
7.10 KB,
patch
|
rail
:
review+
catlee
:
checked-in+
|
Details | Diff | Splinter Review |
Right now the build prioritization function loads *all* pending builds, and only examines the first one. getBuildable() accepts a count argument, so we should use that.
Assignee | ||
Comment 1•14 years ago
|
||
Attachment #495782 -
Flags: review?(rail)
Comment 2•14 years ago
|
||
Comment on attachment 495782 [details] [diff] [review] Refactor builder priority function, make it faster Looks fine, except of the fact that one the hunks is bitrotten.
Attachment #495782 -
Flags: review?(rail) → review+
Assignee | ||
Comment 3•14 years ago
|
||
Comment on attachment 495782 [details] [diff] [review] Refactor builder priority function, make it faster on default changeset: 3380:45fbfd1a794c
Attachment #495782 -
Flags: checked-in+
Assignee | ||
Updated•14 years ago
|
Flags: needs-reconfig?
Updated•14 years ago
|
Flags: needs-reconfig? → needs-reconfig+
Assignee | ||
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•