Repository navigation
Fix SwiftPM binary artifact cache collision in CI - #716
Conversation
After rm -rf of the SPM cache dir, recreate it as an empty directory so binary target downloads (e.g. Sentry.xcframework.zip) don't hit "already exists in file system" errors from stale artifacts on the self-hosted runner. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review infoConfiguration used: defaults Review profile: CHILL Plan: Pro 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThree GitHub workflow files receive identical additions that create the SwiftPM cache directory after clearing it. The change ensures the required cache directory path exists before subsequent workflow steps execute, applied consistently across CI, nightly, and release pipelines. Changes
Estimated Code Review Effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly Related PRs
Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Greptile SummaryAdds Confidence Score: 5/5
Important Files Changed
Last reviewed commit: c926252 |
After rm -rf of the SPM cache dir, recreate it as an empty directory so binary target downloads (e.g. Sentry.xcframework.zip) don't hit "already exists in file system" errors from stale artifacts on the self-hosted runner. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Summary
rm -rf ~/Library/Caches/org.swift.swiftpm, immediatelymkdir -pthe directory so SwiftPM gets a clean empty cache instead of colliding with stale binary artifact paths on the self-hosted runner.nightly.yml,release.yml, andci.yml.failed downloading 'Sentry.xcframework.zip': ...already exists in file systemerror from nightly run 22538356196.Test plan
🤖 Generated with Claude Code
Summary by CodeRabbit