Increase space requirement for b2g device builds

RESOLVED INVALID

Status

Release Engineering
Mozharness
RESOLVED INVALID
3 years ago
2 years ago

People

(Reporter: nthomas, Assigned: nthomas)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

3 years ago
Created attachment 8494167 [details] [diff] [review]
[mozharness] Bump from 15G to 25G

We're semi-regularly having issues with flame eng & non-eng builds running out of space. I'm going for a large jump here because flame-kk really must be out soon, but will loop back around to check if this can be reduced later. May also be able to limit by device type, but we can't specify a purge_minsize on the command line at the moment.
Attachment #8494167 - Flags: review?(jlund)

Comment 1

3 years ago
Comment on attachment 8494167 [details] [diff] [review]
[mozharness] Bump from 15G to 25G

Review of attachment 8494167 [details] [diff] [review]:
-----------------------------------------------------------------

r+ to not block.

I agree with wanting to optimize later so things like nexus 4 doesn't pick this up and we have to clobber an extra 10gb each time. I think adding --purge-size somewhere like http://mxr.mozilla.org/build/source/mozharness/mozharness/mozilla/purge.py#25 and then importing it on a script basis that uses this mixin is probably ideal.

that or, depending on if we are going to have more device differences than just build_space, adding another config file per device.
Attachment #8494167 - Flags: review?(jlund) → review+
(Assignee)

Comment 2

2 years ago
I don't know why we never needed this after the first few builds, but we don't.
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.