-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Fix symlinked swift-experimental-destination
invocations
#6382
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 experimental-destination` subcommands no longer work and always display help output. This is a regression introduced in #6362 after making `SwiftDestinationTool` conform to `AsyncParsableCommand` instead of `ParsableCommand` but not updating `swift-package-manager` command sources to call `async` overload of `main()` function on `SwiftDestinationTool`. rdar://107618266
@@ -22,14 +22,14 @@ let execName = (try? AbsolutePath(validating: firstArg).basenameWithoutExt) ?? | |||
|
|||
@main | |||
struct SwiftPM { | |||
static func main() { | |||
static func main() async { |
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'm not sure we can do this until the CI has been updated to macOS 12?
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.
You're right 😭
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.
main.swift here we come
@swift-ci smoke test |
Sporadic macOS test failure?
|
@swift-ci smoke test macos |
`swift experimental-destination` subcommands no longer work and always display help output. This is a regression introduced in #6362 after making `SwiftDestinationTool` conform to `AsyncParsableCommand` instead of `ParsableCommand` but not updating `swift-package-manager` command sources to call `async` overload of `main()` function on `SwiftDestinationTool`. rdar://107618266
_ = try await withTemporaryDirectory( | ||
fileSystem: fileSystem, | ||
) throws { | ||
_ = try withTemporaryDirectory( |
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.
The downside of this change is that non-async withTemporaryDirectory
does not take a FileSystem
argument, which makes it harder to test. But this is the only way until our macOS CI nodes have Xcode with support for concurrency back-deployment.
@swift-ci smoke test |
@swift-ci test windows |
1 similar comment
@swift-ci test windows |
@swift-ci smoke test windows |
@swift-ci smoke test |
@swift-ci test windows |
@swift-ci smoke test macos |
@swift-ci test windows |
@swift-ci smoke test macos |
swift experimental-destination
subcommands no longer work and always display help output. This is a regression introduced in #6362 after makingSwiftDestinationTool
conform toAsyncParsableCommand
instead ofParsableCommand
but not updatingswift-package-manager
command sources to callasync
overload ofmain()
function onSwiftDestinationTool
.rdar://107618266