Closed
Bug 940385
Opened 12 years ago
Closed 12 years ago
Hazard builds need to purge more than 10G
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: sfink)
References
Details
Attachments
(1 file)
|
1018 bytes,
patch
|
mozilla
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
Bug 939324 has us purging at the start of the hazard builds, but not asking for enough space:
http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/fx-team-linux64-br-haz/1384763379/linux64-br-haz_fx-team_dep-bm64-build1-build2.txt.gz
| Reporter | ||
Comment 1•12 years ago
|
||
I looked at some inbound hazard builds (fx-team ones were all gone) and they tend to use 10850MB after the build. Could we be peaking at higher than that during the build ?
Flags: needinfo?(sphink)
| Assignee | ||
Comment 2•12 years ago
|
||
Wow. Uh, yeah, it's possible. The builds are pretty huge, though I hadn't realized they got *that* big. In particular, there is a very large, very redundant gcFunctions.txt file that is generated and then compressed (one example file goes from 200MB uncompressed to 3.2MB compressed).
But dang, 10GB??!
Flags: needinfo?(sphink)
| Assignee | ||
Comment 3•12 years ago
|
||
Let's see if I can blow through 15GB.
Attachment #8334648 -
Flags: review?(aki)
| Assignee | ||
Updated•12 years ago
|
Assignee: nobody → sphink
Status: NEW → ASSIGNED
Updated•12 years ago
|
Attachment #8334648 -
Flags: review?(aki) → review+
| Assignee | ||
Comment 4•12 years ago
|
||
| Assignee | ||
Comment 5•12 years ago
|
||
Comment 6•12 years ago
|
||
Comment on attachment 8334648 [details] [diff] [review]
Require 15GB free space for hazard builds
In production.
Attachment #8334648 -
Flags: checked-in+
Comment 7•12 years ago
|
||
something[s] here made it to production
| Assignee | ||
Updated•12 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•