Skip to content

Conversation

@compnerd
Copy link
Member

We always install the swift module into the platform directory. The additional nesting is not required.

We always install the swift module into the platform directory. The
additional nesting is not required.
@compnerd
Copy link
Member Author

@swift-ci please test

@grynspan grynspan added bug 🪲 Something isn't working build 🧱 Affects the project's build configuration or process labels Mar 14, 2025
@grynspan grynspan added this to the Swift 6.2 milestone Mar 14, 2025
@grynspan
Copy link
Contributor

Is this broken on specific platforms?

@compnerd
Copy link
Member Author

It is broken on all platforms, except hidden by the fact that it is behind the disabled by default option of Testing_INSTALL_NESTED_SUBDIR.

@stmontgomery
Copy link
Contributor

@compnerd Can you do a cross-repo build and ensure both smoke test and toolchain builds succeed?

@grynspan
Copy link
Contributor

Please squash when you merge!

@compnerd
Copy link
Member Author

Kicked off some tests at swiftlang/swift#65907

@compnerd
Copy link
Member Author

compnerd commented Mar 14, 2025

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.

@compnerd compnerd merged commit efc39a5 into swiftlang:main Mar 14, 2025
3 checks passed
@compnerd compnerd deleted the nesting branch March 14, 2025 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug 🪲 Something isn't working build 🧱 Affects the project's build configuration or process

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants