Conversation
added 7 commits
September 13, 2026 19:52
The release DMG is cut on Xcode 26.3 while CI pinned 26.6, so a CGFloat/Double ambiguity in WorkTimeCanvas.swift passed every check and broke only the release build. This leg runs build-app.sh's exact command (swift build -c release) under the release toolchain.
The release DMG is cut on macOS 15.7 with Xcode 26.3; a lone Xcode pin on macos-26 did not reproduce the release-only compile failure, so pin the runner image too.
Collaborator
Author
|
Closing without merging. The failure this job guarded against (ambiguous use of operator '-' in WorkTimeCanvas.swift on the release machine) could not be reproduced anywhere: Xcode 26.0.1-26.6 on macos-15/macos-26, Xcode 16.4, Swift 5/6 modes, a Swift main snapshot, and x86_64 cross-builds all compile the pre-fix revision (5aff13a) cleanly. No local session, transcript, or ledger records the diagnostic either. Per Frank: not reproducible here, so not a bug we should fix. The clarifying fix (#212) is already merged and harmless. Reopen if a release-machine build log ever surfaces. |
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.
Problem
PR #190 passed every CI check yet main could not be built into a signed DMG on the release machine (reported: macOS 15.7 / Xcode 26.3,
swift build -c releasefailing withambiguous use of operator '-'inWorkTimeCanvas.swift). #212 carries the three-line fix.Change
Adds
macos-release-build:macos-15(the release OS) withXcode_26.3(the release toolchain), runningswift build -c releaseinapps/agentacct— exactlybuild-app.sh's compile command.Reproduction status: not yet achieved (full matrix below)
Building the broken pre-fix revision (
5aff13a) succeeds on everything reachable:macos-26macos-15(log verified "Xcode 26.3", 17C529)macos-15Searches of local transcripts, the agentacct ledger and the Swift issue tracker found no matching diagnostic or documented regression. Conclusion: the release-only failure is not reproducible with any toolchain, SDK or language configuration available here; it is specific to that machine's environment.
What is needed to make this leg a true reproducer
Run on the release machine and paste the output:
The first error block from
/tmp/release-build.logplus those three version lines will identify the toolchain/state that fails (candidate explanations: a beta/regressed Swift build behind "26.3", a CommandLineTools-vs-Xcode mismatch, or stale incremental state). If it is a swift.org or beta toolchain, this job will pin that exact version.Until then this check is release-OS/toolchain parity and defense-in-depth; it is not claimed to catch the #212 class.