-
Notifications
You must be signed in to change notification settings - Fork 105
build: avoid doubly nesting the swift module #1025
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
We always install the swift module into the platform directory. The additional nesting is not required.
@swift-ci please test |
Is this broken on specific platforms? |
It is broken on all platforms, except hidden by the fact that it is behind the disabled by default option of |
@compnerd Can you do a cross-repo build and ensure both smoke test and toolchain builds succeed? |
Please squash when you merge! |
Kicked off some tests at swiftlang/swift#65907 |
All tests (smoke test Linux, macOS, Windows & build toolchain Linux, macOS, Windows) except Windows Testing passed. The Windows Toolchain build succeeded, and a second run at swiftlang/swift#79932 passed. I'm going to merge this as all the builds seem to have passed and the one failure is a flake. |
We always install the swift module into the platform directory. The additional nesting is not required.