-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
swift-testing does not build with ToT SwiftPM #7479
Comments
The new swift-foundation does not build either since the April 21 trunk snapshot of the linux toolchain:
The prior April 13 trunk snapshot works fine. @MaxDesiatov, maybe you know what's going on here. |
We're now seeing it on Linux too. https://ci.swift.org/job/pr-swift-testing-linux-5.10/683/console |
Our current suspicion is that this may have been caused by #7353 |
I can confirm that reverting #7353 again gets swift-foundation building on linux with the latest April 22 trunk snapshot of the toolchain. |
Modified `ResolvedModule` build triples were not reflected in `ResolvedPackage`, which meant those modules aren't included in the build graph. Verified with `swift-foundation` and `swift-testing` packages. Resolves #7479.
Modified `ResolvedModule` build triples were not reflected in `ResolvedPackage`, which excluded those modules from the build graph. Verified manually with `swift-foundation` and `swift-testing` packages. More comprehensive automated tests will be included in a future PR. Resolves #7479.
Modified `ResolvedModule` build triples were not reflected in `ResolvedPackage`, which excluded those modules from the build graph. Verified manually with `swift-foundation` and `swift-testing` packages. More comprehensive automated tests will be included in a future PR. Resolves swiftlang#7479.
Modified `ResolvedModule` build triples were not reflected in `ResolvedPackage`, which excluded those modules from the build graph. Verified manually with `swift-foundation` and `swift-testing` packages. More comprehensive automated tests will be included in a future PR. Resolves swiftlang#7479.
Modified `ResolvedModule` build triples were not reflected in `ResolvedPackage`, which excluded those modules from the build graph. Verified manually with `swift-foundation` and `swift-testing` packages. More comprehensive automated tests will be included in a future PR. Resolves #7479. (cherry picked from commit b9eb3c1) # Conflicts: # Sources/PackageGraph/ModulesGraph+Loading.swift # Sources/PackageGraph/Resolution/ResolvedPackage.swift
A recent Swift Package Manager change seems to have regressed swift-testing:
https://ci.swift.org/job/pr-swift-testing-macos/633/
The text was updated successfully, but these errors were encountered: