-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Add tags to Swift Testing Tests #9292
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
Add tags to Swift Testing Tests #9292
Conversation
|
@swift-ci test |
5951fe8 to
3ab4cbe
Compare
|
@swift-ci test |
|
@swift-ci test windows |
3ab4cbe to
d7b534f
Compare
|
@swift-ci test |
|
@swift-ci test windows |
| /// Which compile-time sanitizers should be enabled. | ||
| @Option( | ||
| name: .customLong("sanitize"), | ||
| help: "Turn on runtime checks for erroneous behavior, possible values: \(Sanitizer.formattedValues)." |
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.
Was this accidentally added from a different PR?
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.
it was not. swift argument parser library lists the possible values, so the redundant text was removed.
| .Feature.CommandLineArguments.Configuration, | ||
| ), | ||
| .tags( | ||
| .Feature.CommandLineArguments.VeryVerbose, |
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.
These tags feel very fine-grained and hard to individually maintain, should we use something more general?
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.
These tags are currently being used to determine command line feature parity between SwiftBuild and native build system.
| .SWBINTTODO("Test fails because the dummy-swiftc used in the test isn't accepted by swift-build. This needs to be investigated"), | ||
| arguments: getBuildData(for: SupportedBuildSystemOnPlatform), | ||
| .tags( | ||
| .Feature.EnvironmentVariables.SWIFT_EXEC, |
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.
Same question here, I'm not 100% convinced tags for individual env vars makes sense
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 would tend to agree, but we need to track the feature parity between native and SwiftBuild. This is one way to track which environment variables are added.
|
@swift-ci test self hosted windows |
relates to: #9287