New issue
Advanced search Search tips

Issue 757251 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Aug 31
Cc:
no...@chromium.org
estaab@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Feature



Sign in to add a comment

Revisit how & whether cleanup_disk cleans up output directories

Project Member Reported by jbudorick@chromium.org, Aug 20 2017 
I removed output directory deletion from cleanup_disk in https://chrome-internal.googlesource.com/infra/infra_internal/+/f0e1674d9e1c55cd6069fea56838337e4265e589 because it interfered with live builds. Once we have the ability to keep it from doing so, we should revisit how cleanup_disk interacts with output directories.

Comment 1 by s...@google.com, Aug 31 2017

Cc: estaab@chromium.org no...@chromium.org
Status: Available (was: Untriaged)
Could be a candidate for the global infra lock. Or with LUCI on Swarming we should hopefully not have such disk space issues in the first place.

Comment 2 by no...@chromium.org, Aug 31 2017 

indeed, swarming manages bot disk and cleans up after tasks (unless explicitly told otherwise (named caches))
Project Member

Comment 3 by sheriffbot@chromium.org, Aug 31

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by hinoka@chromium.org, Aug 31

Status: WontFix (was: Untriaged)
I don't think this is an issue in LUCI since swarming fully manages free space on its own bots.
►

Sign in to add a comment