Closed
Bug 476390
Opened 16 years ago
Closed 16 years ago
Update required free space for win32 builds
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: nthomas)
Details
Attachments
(1 file)
3.71 KB,
patch
|
catlee
:
review+
nthomas
:
checked-in+
|
Details | Diff | Splinter Review |
The mozilla-central nightly failed for win32 today. There was a problem in complete mar generation
...
ignoring remove instruction for directory: extensions/{641d8d09-7dda-4850-8228-ac0ab65e2ac9}/
ignoring remove instruction for directory: searchplugins/
ignoring remove instruction for directory: extensions/talkback@mozilla.org/
mv: cannot stat `../../dist/firefox.work/output.mar': No such file or directory
Nagios also reported free disk was down to 22MB at 6:17 PST, about 20 minutes after the build failed out on moz2-win32-slave01.
Luckily the build dir was still present on the slave and windows explorer reports that
/e/builds/moz2_slave/mozilla-central-win32-nightly/build
has Size of 4.62GB, and Size on Disk of 5.92GB. We're probably hitting this problem as the mercurial repo's grow.
This patch bumps the free space at the start of the run from 6GB to 7GB to give us back some headroom, for both m-c and m-1.9.1 as the repo size and builds are similar. It drops it for tracemonkey since a couple of the most recent builds are using only 3.36 GB on disk (presumably because we're not PGO'ing there).
Attachment #360022 -
Flags: review?(catlee)
Updated•16 years ago
|
Attachment #360022 -
Flags: review?(catlee) → review+
Assignee | ||
Comment 1•16 years ago
|
||
Comment on attachment 360022 [details] [diff] [review]
Update required space for win32
Pushed to repo and production-master reconfig'd.
Attachment #360022 -
Flags: checked‑in+ checked‑in+
Assignee | ||
Updated•16 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Priority: -- → P2
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
•