[test] Move test/attr/attr_availability_transitive_osx_appext.swift to fake version #76132
Conversation
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
…o fake version Keep this test independent of the default deployment target by using a larger version number.
|
@swift-ci please test |
tshortli
approved these changes
Aug 28, 2024
|
Probably not worth changing now, but did you try specifying an explicit |
|
Explicit target would work too, and some tests can only be handled that way (e.g. #76027 has a bunch), but the dominant style seemed to be using fake versions (e.g. #76023), so that's what I stuck with where it was possible. I don't really care either way, just trying to be consistent with the other availability tests. |
benlangmuir
deleted the
test-fake-version-attr_availability_transitive_osx_appext
branch
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.
Keep this test independent of the default deployment target by using a larger version number.
This is a follow-on to #76023 for a test that was recently changed