Need larger disk slave for vm18-m1 |
||
Issue descriptionDerived from https://bugs.chromium.org/p/chromium/issues/detail?id=801824 "Mac Goma Canary LocalOutputCache" builder needs 120GB output + 30GB LocalOutputCache + ~50GB others for disk. "Mac Goma Canary LocalOutputCache" is now running on vm18-m1, which has 200GB disk. 200GB disk is a bit short for the builder, so chrome-trooper gets an alert that free disk space is below 5%. Can we move this builder to a VM that has more disk? 250GB should be enough.
,
Jan 22 2018
> Can we move this builder to a VM that has more disk? 250GB should be enough. Old disk: $ diskutil list disk0 /dev/disk0 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *214.7 GB disk0 New disk: $ diskutil list disk0 /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *251.0 GB disk0 and for compairson.. a Mac Mini disk: $ diskutil list disk0 /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *251.0 GB disk0 VMs now will match Mac Minis as far as disk space (as they should have matched Minis to begin with). If you're still needing more disk space the only other thing we can do put you in line for waiting on a Mac Pro (we don't have any free currently, and there will be a multi-quarter wait currently).
,
Jan 23 2018
Thank you! |
||
►
Sign in to add a comment |
||
Comment 1 by d...@chromium.org
, Jan 19 2018Status: Assigned (was: Untriaged)