From 14fc9922d7b4c2db69b7c24e98caf82a961157bc Mon Sep 17 00:00:00 2001 From: Sunmin Lee <134378502+sunm2n@users.noreply.github.com> Date: Fri, 4 Sep 2026 17:46:09 +0900 Subject: [PATCH] docs: fix arithmetic in build cache GC policy example The GC policy example defines the first policy as "delete records until there's maximum 5GB of stale cache left", then describes a sweep over 11GB of cache (7GB stale, 4GB other) as deleting 5GB and leaving 6GB. Both numbers contradict the policy as defined. Keeping a maximum of 5GB of stale cache means deleting 2GB of the 7GB, which leaves 5GB stale plus 4GB other, for 9GB in total. The 6GB figure only follows from reading the policy as "delete 5GB", which is the opposite of what it says. The example's point is unchanged: 9GB is still under the second policy's 10GB limit, so the second policy does not need to clear any more cache. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01TGSfAZyRTEw9qGGzVECGYk Signed-off-by: Sunmin Lee <134378502+sunm2n@users.noreply.github.com> --- content/manuals/build/cache/garbage-collection.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/manuals/build/cache/garbage-collection.md b/content/manuals/build/cache/garbage-collection.md index 7609bab11a08..c80a98a544b9 100644 --- a/content/manuals/build/cache/garbage-collection.md +++ b/content/manuals/build/cache/garbage-collection.md @@ -47,8 +47,9 @@ you have 11GB worth of build cache, where: - 7GB of which is "stale" cache - 4GB is other, more valuable cache -A GC sweep would delete 5GB of stale cache as part of the 1st policy, with a -remainder of 6GB, meaning the 2nd policy does not need to clear any more cache. +A GC sweep would delete 2GB of stale cache as part of the 1st policy, leaving +9GB of cache in total, meaning the 2nd policy does not need to clear any more +cache. The default GC policies are (approximately):