[8.7.0] Deduplicate identical repo contents cache entries during GC #29071
Merged
Conversation
Such entries are created when multiple Bazel servers fetch the same repo at the same time and waste space. This has been tested manually by running many concurrent Bazel commands with different output bases. After the specified idle delay, only a single repo remained for each entry and subsequent runs with all these output bases succeeded and shared that one entry. Closes bazelbuild#26682. PiperOrigin-RevId: 797358986 Change-Id: Ib6dc5f718a8e8e1e76b1e2804ad6ada765baee1e (cherry picked from commit 9bb6c19)
fmeum
changed the title
fmeum
changed the title
github-actions
Bot
added
team-ExternalDeps
meteorcloudy
approved these changes
Apr 1, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
github-actions
Bot
removed
the
awaiting-review
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Such entries are created when multiple Bazel servers fetch the same repo at the same time and waste space.
This has been tested manually by running many concurrent Bazel commands with different output bases. After the specified idle delay, only a single repo remained for each entry and subsequent runs with all these output bases succeeded and shared that one entry.
Closes #26682.
PiperOrigin-RevId: 797358986
Change-Id: Ib6dc5f718a8e8e1e76b1e2804ad6ada765baee1e
(cherry picked from commit 9bb6c19)