Closed
Bug 472884
Opened 16 years ago
Closed 16 years ago
add suitable buildSpace arguments release builders
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
References
Details
Attachments
(3 files, 1 obsolete file)
|
959 bytes,
patch
|
catlee
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
|
7.51 KB,
patch
|
catlee
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
|
1.15 KB,
patch
|
bhearsum
:
review+
nthomas
:
checked-in+
|
Details | Diff | Splinter Review |
Especially right now when free space is scarce it's important to make sure release builders aren't failing out due to lack of space.
| Assignee | ||
Updated•16 years ago
|
Priority: -- → P2
| Assignee | ||
Comment 1•16 years ago
|
||
These are pretty sensible defaults, I think. For steps that grow as we add a locale, as sourceRepo gets bigger, etc. I've added some breathing room - we shouldn't have to update them for quite awhile. Eg, L10nVerify downloads all the builds - currently approx. 12G, but will grow quickly as we add more locales.
Attachment #357351 -
Flags: review?(catlee)
Comment 2•16 years ago
|
||
Comment on attachment 357351 [details] [diff] [review]
add sensible default buildSpace parameters to release factories
I'm pretty sure purge_builds doesn't support non-integer sizes at this point.
| Assignee | ||
Comment 3•16 years ago
|
||
Attachment #357353 -
Flags: review?(catlee)
| Assignee | ||
Comment 4•16 years ago
|
||
Attachment #357351 -
Attachment is obsolete: true
Attachment #357354 -
Flags: review?(catlee)
Attachment #357351 -
Flags: review?(catlee)
Updated•16 years ago
|
Attachment #357353 -
Flags: review?(catlee) → review+
Updated•16 years ago
|
Attachment #357354 -
Flags: review?(catlee) → review+
| Assignee | ||
Comment 5•16 years ago
|
||
Comment on attachment 357353 [details] [diff] [review]
s/int/float/ for purge_builds
changeset: 35:02c4d3fa5170
Attachment #357353 -
Flags: checked‑in+ checked‑in+
| Assignee | ||
Updated•16 years ago
|
Attachment #357354 -
Flags: checked‑in+ checked‑in+
| Assignee | ||
Comment 6•16 years ago
|
||
Comment on attachment 357354 [details] [diff] [review]
buildSpace + exclusion list fix
Checking in process/factory.py;
/cvsroot/mozilla/tools/buildbotcustom/process/factory.py,v <-- factory.py
new revision: 1.80; previous revision: 1.79
done
| Assignee | ||
Comment 7•16 years ago
|
||
master reconfig'ed
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 8•16 years ago
|
||
Need to provide a bit more space for the update generation step, it accumulates quite a lot of files as it goes along. Data and a patch coming up.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 9•16 years ago
|
||
Before generating partials, you need
651 MB mozilla/ checkout
~ 35MB per locale for previous release's complete mars
~ 35MB per locale for current release's complete mars
While producing partials, you need
Linux: 54MB + (N-1)*24MB for N locales
Mac: 100MB + (N-1)*42MB
Win32: 54MB + (N-1)*29MB
for working space.
For the 64 locales for 3.1b3 (really 63, but we still process both ja locales), that means 2250MB for each set of complete mars, and roughly 6210MB in work space. About 600MB of partial updates are created, so you'd need about 11.7GB just before the work dir was cleared up.
Add a bit of padding to come up with 13GB - about 8 locales worth, it's about 175MB/locale all up.
Attachment #359684 -
Flags: review?(bhearsum)
| Assignee | ||
Comment 10•16 years ago
|
||
Comment on attachment 359684 [details] [diff] [review]
Allow 13GB instead of 8
Sounds good!
Attachment #359684 -
Flags: review?(bhearsum) → review+
Updated•16 years ago
|
Attachment #359684 -
Flags: checked‑in+ checked‑in+
Updated•16 years ago
|
Status: REOPENED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•