-
Notifications
You must be signed in to change notification settings - Fork 138
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
Fetch the Swift toolchain as part of the CI job #672
Conversation
I don't really understand why the builds are failing with this error, independent of the Swift version:
Will continue to investigate... |
I think a commit was merged ignoring the failing CI, so it's possible it introduce a bug |
I can try to rebase on the last passing commit to check whether this PR works as intended. Which Swift version would you prefer to use? |
newest release version (so 5.4.x) would be ideal, but realistically the difference in the minor releases above 5 should be inconsequential for CI here, so if you can get one of these working I'm happy to merge and potentially update later |
That seems to work. I will be able to find the culprit that way and will let you know here :) |
fa394a4
to
1366ac1
Compare
Results: Up to commit b0ea825 your CI was green: https://buildkite.com/bazel/rules-swift-swift/builds/2733 The next commit 8cf3635 broke the build, but with a different error message and across all platforms: https://buildkite.com/bazel/rules-swift-swift/builds/2734#9d2420e3-d852-48e4-9dca-9c546fce5a82 The next commit 93a91f4 seems to have fixed it on macOS, but from that commit on your Linux builds are failing with the strange crash visible at HEAD, too: https://buildkite.com/bazel/rules-swift-swift/builds/2735#3b4e3037-2b9b-469f-8768-300479e885a3 |
I'll rebase this against master and then we can just submit this so that your CI works, then you can look at how to fix this breakage much more easily :) |
I'm trying to remove parts from our Docker containers that are only used by one or few projects on CI. Instead, we can download & extract them during the shell_commands step of the projects. This also allows the projects themselves to control the exact versioning of their dependencies and makes it easier to test upgrades.
Done. Feel free to merge. |
Thanks! |
I'm trying to remove parts from our Docker containers that are only used by one or few projects on CI.
Instead, we can download & extract them during the shell_commands step of the projects. This also allows the projects themselves to control the exact versioning of their dependencies and makes it easier to test upgrades.