ci(macos): salt mcpp sandbox cache (std.pcm deployment-target mismatch)#318
Merged
Conversation
…match) The workflow pins MACOSX_DEPLOYMENT_TARGET=11.0, but the cached ~/.mcpp BMI store contains a std.pcm built for arm64-apple-macosx15 under the same fingerprint — mcpp <= 0.0.49 does not include the deployment target in the BMI fingerprint, so the stale module is reused and every TU fails with a config mismatch. Salt the cache so a coherent (all-11.0) store is rebuilt. mcpp 0.0.50 folds the deployment target into the fingerprint, fixing this class permanently (mcpp-community/mcpp#116).
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.
macos CI on main is red since mcpp 0.0.49 became the index latest: the workflow pins
MACOSX_DEPLOYMENT_TARGET=11.0, but the restored~/.mcppBMI cache holds astd.pcmbuilt forarm64-apple-macosx15under the same fingerprint — mcpp ≤ 0.0.49 doesn't include the deployment target in the BMI fingerprint, so the stale module is reused and every TU dies with:Salting the cache key (+ restore-keys) rebuilds a coherent all-11.0 store. Permanent fix ships in mcpp 0.0.50 (mcpp-community/mcpp#116: deployment target folded into the fingerprint +
[build] macos_deployment_targetmanifest field), after which xlings switches to the manifest field with CI assertions.