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
Verify & Resolve swift package index builds #466
Comments
Odd that recent builds with Swift 5.4 work fine. The watchOS target there breaks because of the XCTest module. The build command is
I don't have Xcode 12.2 on my device at the moment, so I cannot test this right now. The Does this have consequences when using the packages? I think not, so I wouldn't worry about that too much, although it'd be great if someone checked out why their build system fails and Travis doesn't. |
watchOS on Swift 5.1/5.2/5.3The build process tries to use XCTest, which isn't available. Since tests aren't run by the Swift package index servers, I wonder if there's a way to disable test compilation. The
It should read FWIW I cannot reproduce successful builds on my machine when I copy the build command:
So maybe we should raise an issue with Swift package index for this. iOS on Swift 5.1-- but the iOS errors there are pretty simple:
They are using Xcode 11.3.1 for the build. That of course isn't available on M1 Macs :) So I cannot provide a quick fix for these and test these locally at the moment. We could also not make the tests backwards compatible. Again, SwiftPI doesn't run the tests, so compiling them is not necessary. Maybe we can tell SwiftPI to ignore test files in that case. Other packages like RxSwift seem to compile without tests, too, so this might be an issue of the project organization: https://swiftpackageindex.com/builds/F65F733A-80D8-4119-8B52-36FA6263D5B6 |
https://swiftpackageindex.com/ReSwift/ReSwift/builds
Swift package index is a useful resource. We should verify the functionality of each build -- notable is that it indicates the watchOS build is not working. We should verify each failing build and see if there is a way to fix it.
The text was updated successfully, but these errors were encountered: