Closed Bug 541282 Opened 16 years ago Closed 16 years ago

Bump build space for win32 opt builds

Categories

(Release Engineering :: General, defect)

x86
Windows Server 2003
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nthomas, Assigned: bhearsum)

References

Details

(Whiteboard: [automation])

Attachments

(1 file)

We had 3 failed attempts at building a m-c win32 nightly today, two of which failed in make installer/package (the other was bug 509960). Both ran on slaves with FAT disks that had 8.1G free when asked for 8G, and we know FAT uses more space than NTFS does. Since we decided to stop upgrading slaves (bug 489940) we should bump the requirement to 9G. Taking the liberty of assigning this to bhearsum as build-duty person this week.
Attachment #422900 - Flags: review?(bhearsum)
I should say that the big jumps for places and electrolysis are probably due to them not creating test packages and updates and so on. Keeping them in sync with m-c should mean less churn when we're asked to start running packaged unit tests and other builds types on those branches.
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1264117955.1264132020.28871.gz WINNT 5.2 mozilla-central build on 2010/01/21 15:52:35 s: win32-slave05 Not even a nightly, died in make package-tests after starting with 8.02 GB.
Comment on attachment 422900 [details] [diff] [review] Bump requirement to 9G I'll land this today
Attachment #422900 - Flags: review?(bhearsum) → review+
Comment on attachment 422900 [details] [diff] [review] Bump requirement to 9G changeset: 1990:53b4b52e1709
Attachment #422900 - Flags: checked-in+
The masters have been reconfiged.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: