New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove previously deprecated --enable-test-discovery
#7391
Conversation
This flag was deprecated for 4 years since Swift 5.4, Swift 6.0 is a good opportunity to remove it.
@swift-ci test |
@swift-ci test |
@swift-ci test windows |
Sources/SPMBuildCore/BuildParameters/BuildParameters+Testing.swift
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've asked @stmontgomery to also review this change, but I'm glad to see this flag go.
I think there are some unit tests you'll also need to revise or delete while you're in here.
@swift-ci test |
@swift-ci test windows |
@swift-ci test |
@swift-ci test windows |
@swift-ci test |
@swift-ci test windows |
@swift-ci test windows |
Sounds good, we only support swift 5.7+ nowadays in most telos so we can drop it I think. Swift log I think supports ancient versions but we can maybe stop testing on them or something... I'll think about it |
Thanks for the heads-up @MaxDesiatov.
Is
We have repos that pass @ktoso I guess we should consider bumping up the Swift version requirement if we run into trouble removing |
It's only ignored when you pass |
Got it. Thanks @MaxDesiatov. |
Don't we want to stop using it? |
IDK, if we do we'd have to go through a deprecation cycle with those for at least a few releases first. This PR is about that one test discovery flag specifically. |
Reverts #7391, which blocks CI as various projects are still using `--enable-test-discovery`.
This flag was deprecated for 4 years since Swift 5.4, Swift 6.0 is a good opportunity to remove it.
Closes #7389.