Closed
Bug 888454
Opened 12 years ago
Closed 12 years ago
Increase build_space for linux32 builds
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: philor, Assigned: philor)
Details
Attachments
(1 file)
3.72 KB,
patch
|
catlee
:
review+
philor
:
checked-in+
|
Details | Diff | Splinter Review |
purge_actual: '9.16GB', purge_target: '9GB', IOError: [Errno 28] No space left on device
Might as well jump up to 12, it seems to be working for all the linux64s that recently went there.
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → philringnalda
Assignee | ||
Comment 1•12 years ago
|
||
Where by "working" I meant to say "not working" since https://tbpl.mozilla.org/php/getParsedLog.php?id=24698612&tree=Birch&full=1 is a linux64 freeing 12.14GB and running out. Thanks, gtest-linking-libxul-twice and packaging-unstripped-cppunittests!
Assignee | ||
Comment 2•12 years ago
|
||
Probably a better idea would be for someone to figure out what, if anything, is actually using default_build_space (not Spidermonkey, like I thought at first, they pass 4 on their own commandline), switch it to 14 and make a few exceptions be the only things not to use it.
Attachment #769523 -
Flags: review?(catlee)
![]() |
||
Updated•12 years ago
|
Attachment #769523 -
Flags: review?(catlee) → review+
![]() |
||
Comment 3•12 years ago
|
||
Fixing the default sounds great. Also, some early warning that we're approaching the current free space limit would be awesome. Some alert if we end up with <2GB free?
Assignee | ||
Comment 4•12 years ago
|
||
Comment on attachment 769523 [details] [diff] [review]
Whack more moles
https://hg.mozilla.org/build/buildbot-configs/rev/ccc4ac5427ab
Attachment #769523 -
Flags: checked-in+
Comment 5•12 years ago
|
||
in production
Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
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
•