Temporarily change to build master-next against swift-5.0-branch of LLVM #18194
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As Swift 4.2 winds down, we're due to move to a newer version of LLVM. The swift-5.0-branch in swift-llvm, swift-clang, and swift-compiler-rt has been updated with content from upstream-with-swift as of last week, and we're planning to adopt this as our next "stable" branch of LLVM (forum announcement should be going out soon). There are still some issues that we need to work through, so to help test that, we're going to temporarily use the master-next bots to build with those branches. We'll switch back to testing against upstream-with-swift after we're done with the transition.
|
@swift-ci smoke test |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As Swift 4.2 winds down, we're due to move to a newer version of LLVM.
The swift-5.0-branch in swift-llvm, swift-clang, and swift-compiler-rt
has been updated with content from upstream-with-swift as of last week,
and we're planning to adopt this as our next "stable" branch of LLVM
(forum announcement should be going out soon). There are still some
issues that we need to work through, so to help test that, we're going
to temporarily use the master-next bots to build with those branches.
We'll switch back to testing against upstream-with-swift after we're
done with the transition.