Restore perception checking tests on macOS #166
Merged
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.
There seem to have been a recent change to the macOS toolchain where both
Testing.frameworkandlibXCTestSwiftSupport.dylibgot built against macOS 14.0 runtime.As a result,
swift test(unless run with both--disable-xctestand--disable-swift-testing) forces the test target to build witharm64-apple-macosx14.0as the minimum deployment target, no matter which lower value thePackage.swiftfile has in itsplatformsarray.This PR adds deprecation annotations on the affected tests, silencing the deprecation warnings, and also skips the failing tests unless the test target it proven to built against an older deployment target1. I set
swift testto build against the older deployment target by passing-target arm64-apple-macosx13.0toswiftcinci.yml. This seems to work, but YMMV.There are two new linker warnings when running tests like this, but I think we can live with them:
With these changes, I think we can restore unit tests in
ci.ymland also include Xcode 26.0.Footnotes
This in turn is a little hack with
@_disfavoredOverload, intentionally symmetrical to what the library already does to hide the backports. ↩