Repository navigation
Conversation
…ifact The macOS Build Binaries leg fails intermittently in `swift build`: the GitHub release CDN answers the Sparkle xcframework download with a short error body (92 bytes on PR #1839, twice in a row), SwiftPM leaves the destination behind in ~/Library/Caches/org.swift.swiftpm/artifacts, and the resolution dies with "... already exists in file system". The script then falls back to swiftc, which cannot bundle Sparkle, and the job exits 1 after "Sparkle.framework NOT found". build-swift-app.sh now captures the swift build output; when it shows the download-failure signature it removes the stale Sparkle entries from the SwiftPM artifact cache and the package's .build/artifacts and runs the build once more. A compile error is still reported once, as before. scripts/build-swift-app.test.sh is a hermetic red/green self-test (fake swift/swiftc/curl on PATH, throwaway HOME and package dir) and runs in unit-tests.yml as "Swift Build Script". Two env vars exist for it only: BUILD_SWIFT_APP_SWIFT_DIR and BUILD_SWIFT_APP_STOP_AFTER_BUILD. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Deploying mcpproxy-docs with
|
| Latest commit: |
21eb451
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://ffa81b10.mcpproxy-docs.pages.dev |
| Branch Preview URL: | https://claude-swift-build-sparkle-r.mcpproxy-docs.pages.dev |
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Contributor
📦 Build ArtifactsWorkflow Run: View Run Available Artifacts
How to DownloadOption 1: GitHub Web UI (easiest)
Option 2: GitHub CLI gh run download 42499958334 --repo smart-mcp-proxy/mcpproxy-go
|
This branch has not been deployed
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
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.
Summary
The macOS Build Binaries leg fails intermittently inside
swift build: the GitHub release CDN answers the Sparkle xcframework download with a short error body (92 bytes, twice in a row on #1839), SwiftPM leaves the destination behind in~/Library/Caches/org.swift.swiftpm/artifacts, and the resolution dies with... already exists in file system. The script then falls back toswiftc, which cannot bundle Sparkle, and the job exits 1 afterSparkle.framework NOT found.scripts/build-swift-app.shcaptures theswift buildoutput; on the download-failure signature (failed downloading/already exists in file system) it purges the stale Sparkle entries from the SwiftPM artifact cache and the package's.build/artifacts, then runs the build once more. A compile error is still reported once, as before.scripts/build-swift-app.test.sh: hermetic red/green self-test (fakeswift/swiftc/curlon PATH, throwaway HOME and package dir) covering stale-artifact retry, compile-error no-retry, and clean first-time build. Wired intounit-tests.ymlas Swift Build Script.BUILD_SWIFT_APP_SWIFT_DIR,BUILD_SWIFT_APP_STOP_AFTER_BUILD.Test plan
bash scripts/build-swift-app.test.sh→ 14/14 (failed 4/14 before the fix)bash -nunder the system bash 3.2; shellcheck adds no new findings🤖 Generated with Claude Code