Free DerivedData before iOS CI builds to fix disk-full archive failures - #1037
Merged
Conversation
The self-hosted Mac runner never purges Xcode's DerivedData across builds, which eventually fills the disk and fails linkReleaseFrameworkIosArm64 with "No space left on device" — surfacing downstream as a confusing codesign/ ARCHIVE FAILED tail that looks unrelated to the real cause. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
1 participant
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.
The self-hosted Mac runner never purges Xcode's DerivedData across builds, which eventually fills the disk and fails linkReleaseFrameworkIosArm64 with "No space left on device" — surfacing downstream as a confusing codesign/ ARCHIVE FAILED tail that looks unrelated to the real cause.