bump space requirements for b2g builds

RESOLVED FIXED

Status

Release Engineering
General
RESOLVED FIXED
6 years ago
19 days ago

People

(Reporter: rail, Assigned: rail)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

I'm not sure if it's related to bug 819368, but Date build  failed to build

It cleaned up ~10G:

10:13:47     INFO - Running command: ['/builds/slave/b2g-date-unagi-dep/scripts/external_tools/purge_builds.py', '-s', '10', '--max-age', '14', '--not', 'info', '--not', 'rel-*', u'/builds/slave']
10:13:47     INFO - Copy/paste: /builds/slave/b2g-date-unagi-dep/scripts/external_tools/purge_builds.py -s 10 --max-age 14 --not info --not rel-* /builds/slave
10:14:30     INFO -  Deleting /builds/slave/m-b2g18-lnx64-dbg
10:14:30     INFO -  10.08 GB of space available

but failed later:

IOError: [Errno 28] No space left on device

Updated

6 years ago
Summary: bump space requirements for b2 builds → bump space requirements for b2g builds
Assignee: nobody → rail
Comment on attachment 696138 [details] [diff] [review]
Add 50%

lgtm
Attachment #696138 - Flags: review?(hwine) → review+
For reference a successful job had |12:23:09     INFO -  14.43 GB of space available|

We have a min purge of 13GB for the ics b2g builds set in buildbot configs, but 10GB set in mozharness, I suggest we bump to 12 or 13

http://mxr.mozilla.org/build/search?string=purge_minsize&find=mozharness&findi=&filter=^[^\0]*%24&hitlimit=&tree=build
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.