-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Unskip all BuildPlanSwiftBuildTests for Swift Build #8503
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
base: main
Are you sure you want to change the base?
Conversation
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.
Oddly enough, there is code that should not compile, but the CI jobs all passed. I have a "blocking" comment, which is simply to remove the whitespace that may have been accidentally inserted in the middle of a variable name.
@@ -6996,27 +6998,19 @@ class BuildPlanSwiftBuildTests: BuildPlanTestCase { | |||
try await super.testDuplicateProductNamesWithNonDefaultLibsThrowError() | |||
} | |||
|
|||
override func testTargetsWithPackageAccess() async throws { |
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.
praise: I love seeing tests added/re-enabled. party🎉
Hmm, I don't think we ran CI in this one Sam. BTW, this is still stacked on this other PR #8454. |
@swift-ci test |
04e20e5
to
db5124f
Compare
586a83f
to
cffbb4a
Compare
@swift-ci please test |
@swift-ci test self hosted windows |
@swift-ci test windows |
@swift-ci test linux |
@swift-ci test macOS |
Motivation:
Increase test coverage for the new PIF builder (for Swift Build).
Modifications:
Enable/unskip all tests in
BuildPlanSwiftBuildTests
when using Swift Build.testTargetsWithPackageAccess
The build error logging, when using
--build-system swiftbuild
, redirects all build tasks command lines toObservabilityScope
, including those checked by this test. These are then redirected to stderr together with all other logging. I feel this makes sense, providing a nice flexibility when filtering theswift build
output, etc.Conversely, the
--build-system native
sends the build tasks command lines to stdout instead.As such, this updates the
testTargetsWithPackageAccess
to reflect that.Result:
All
BuildPlanSwiftBuildTests
are now green on macOS; and just 1 test is skipped on Linux and Windows.