Skip to content
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

Revert the use of generate-pipeline-plugin on Windows platforms. #423

Closed

Conversation

allevato
Copy link
Member

This temporarily removes the use of the plugin only on Windows, where it is not working properly due to a likely bug in SPM. We can keep the files checked in for now and updated using the
Scripts/generate-all-pipelines.sh script, and those files will be ignored on other platforms (the plugin will still be used there).

Fixes #422.

This temporarily removes the use of the plugin only on Windows, where it
is not working properly due to a likely bug in SPM. We can keep the
files checked in for now and updated using the
`Scripts/generate-all-pipelines.sh` script, and those files will be
ignored on other platforms (the plugin will still be used there).

Fixes swiftlang#422.
@allevato
Copy link
Member Author

@compnerd , can you please try this out?

@compnerd
Copy link
Member

compnerd commented Oct 12, 2022

FWIW, ignoring #424, this almost works. swift-argument-parser doesn't build, but that seems unrelated to this? The tests also pass.

Build complete! (28.21s)
[588/588] Testing SwiftFormatRulesTests.ValidateDocumentationCommentsTests/testReturnDocumentation

@allevato
Copy link
Member Author

Closing this in light of #424.

@allevato allevato closed this Oct 12, 2022
@allevato allevato deleted the i-thought-windows-was-plugin-play branch October 12, 2022 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

build on windows, error: plugin process ended by an uncaught signal: 1033
2 participants