-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Provide library paths to plugin tools when run as custom tasks #8767
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
@swift-ci please test |
Use path handling logic from Environment
…ion of runtime library paths
@swift-ci please test |
@swift-ci test Windows |
@@ -182,7 +172,7 @@ final class PluginTests: XCTestCase { | |||
XCTAssert(stdout.contains("Build complete!"), "stdout:\n\(stdout)") | |||
} | |||
|
|||
#if os(macOS) // See https://github.com/swiftlang/swift-package-manager/issues/8416 for errors running build tools on Linux | |||
#if os(macOS) |
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: are these tests not supported on other platform, or they currently fail? If they later, can we convert this Suite to Swift Testing and make use of the withKnownIssue
API instead of skipping the test? This would allow us to "re-enable" the test once the production code gets at par.
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's the latter. I can try and convert these to Swift Testing in a future PR and then we will get notification when features start working, such as with Windows.
@swift-ci please test |
@swift-ci test Windows |
@swift-ci test Linux |
@swift-ci test macOS |
@swift-ci please test |
@swift-ci test Windows |
swiftlang/swift-build#558 and #8767 had a test/merge race which caused a failure in this test on linux. Add a narrow skip to this brand new test until these changes are working together
Linux build tool plugins won't work because they require a library
path to the Swift standard libraries. Add the toolchain's library path
to the environment for the custom task. Enable the tests that cover
this area for non-macOS platforms.