Record the hardlinks in the cache commit message, so we can restore them #828
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.
Description
The git backed build cache duplicates hardlinked files, as git just stores them as multiple files that happen to have the same contents. This means on a cache hit we end up with a package that has duplicated files that were intended to be hardlinks.
Here we record the hardlinks in the install_dir in
#incremental
as they are being added, and add that information as a json blob in the comment of the build cache entry.Later we use that recording in
#restore_from_cache
to restore the observed hardlinks.Closes #827
Maintainers
Please ensure that you check for:
serial number
corresponding change is reviewed and there is a release plan
corresponding change is reviewed and there is a release plan