-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Non-darwin test discovery with Swift Build #8722
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
Conversation
Sources/SwiftBuildSupport/PackagePIFProjectBuilder+Products.swift
Outdated
Show resolved
Hide resolved
Locally, I can pass a decent chunk of TestDiscoveryTests on linux. macOS will need a bit of work to skip building the test runner executables, and I expect Windows will need a few tweaks @swift-ci test |
a18182a
to
10bc51d
Compare
10bc51d
to
401a93f
Compare
@swift-ci test |
401a93f
to
3757526
Compare
@swift-ci test |
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.
Thanks for converting the TestDiscoverTests from XCTest to Swift Testing. I have a couple questions/comments, but nothing blocking.
633a864
to
88ccf4a
Compare
@swift-ci test |
88ccf4a
to
23a8d43
Compare
@swift-ci test |
23a8d43
to
61c3ec0
Compare
@swift-ci test |
9cfbd82
to
e63dc87
Compare
@swift-ci test |
e63dc87
to
70dcd09
Compare
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 only reviewed the tests changes. Although the overcharge is good, we should ensure to run the TestDicoveryTests against SwiftBuild on Windows and use the withKnownIssue
Swift Testing API to essentially mark the test as "expected fail". This will give us signal when the underlying Windows issue is fix, thus prompting the removal of the withKnownIssue
as opposed to having to remember to augment the test.
1b4de2a
to
e73ba32
Compare
@swift-ci test |
@swift-ci test Windows |
Windows: 'TestCommandSwiftBuildTests.testListWithSkipBuildAndNoBuildArtifacts' failed (14.613 seconds) |
e73ba32
to
a180198
Compare
@swift-ci test |
a180198
to
96ab7a9
Compare
@swift-ci test |
struct TestDiscoveryTests { | ||
static var buildSystems: [BuildSystemProvider.Kind] = [BuildSystemProvider.Kind.native, .swiftbuild] | ||
|
||
@Test(arguments: buildSystems) |
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.
suggestion (non-blocking, if-pr-update): using arguments: SupportedBuildSystemOnAllPlatforms
does essentially the same thing :)
} | ||
|
||
func testNonStandardName() async throws { | ||
@Test(.bug("https://github.com/swiftlang/swift-build/issues/13"), arguments: [BuildSystemProvider.Kind.native]) |
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.
question: out of curiosity, why aren't we executing this test against the SwiftBuild build system?
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.
There are some design questions I need to sort out related to response file quoting on non-Darwin platforms and it's not 100% clear to me marking this as a known issue is the right thing to do yet
@swift-ci test windows |
@swift-ci smoke test macOS |
@swift-ci test macOS |
macOS checkout issue |
Still needs a fair amount of work and cleanup, I'll look at breaking off some parts that can land independently. Depends on the larger patch in swiftlang/swift-build#499
Still needs a fair amount of work and cleanup, I'll look at breaking off some parts that can land independently. Depends on the larger patch in swiftlang/swift-build#499