-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Bump Swift version to 4.0 #8861
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
Conversation
@swift-ci clean test |
Build failed |
@swift-ci clean test |
Build failed |
Build failed |
@tkremenek The other place to change is in parser.add_argument(
"--swift-user-visible-version",
help="User-visible version of the embedded Swift compiler",
type=arguments.type.swift_compiler_version,
default="3.1", # change to 4.0
metavar="MAJOR.MINOR") Note: The |
@swift-ci clean test |
Build failed |
Build failed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For now, we need to continue building the standard library and overlays with Swift 3 as well.
on Wed Apr 19 2017, Jordan Rose <notifications-AT-i.8713187.xyz> wrote:
For now, we need to continue building the standard library and
overlays with Swift 3 as well.
That's a little alarming to hear; we've been under the impression that
we could switch to building the standard library in Swift 4 mode
whenever we want. Please explain why not, and when we can expect to be
able to flip the switch.
Thanks,
-Dave
|
@dabrahams makes a good point. The intent is we want the Standard Library and overlays building in Swift 4 mode. |
@DougGregor reminded me offline that the Standard Library/overlays can vend Swift 4 changes with |
@swift-ci clean test |
Build failed |
Build failed |
@swift-ci test linux |
Build failed |
Please test with following pull request: @swift-ci test linux |
Build failed |
Please test with following pull request: @swift-ci test linux |
Build failed |
Please test with following pull request: @swift-ci test linux |
@swift-ci clean test |
Build failed |
Build failed |
This reverts commit 157133d.
… non-macOS platforms.
@swift-ci test |
Build failed |
Build failed |
On Linux it looks like we are down to a test failure in swift-corelibs-Foundation:
|
Please test with following pull request: @swift-ci test linux |
Also seeing on iphoneSimulator:
but this looks like a new, unrelated failure. |
Build failed |
With: swiftlang/swift-corelibs-foundation#972 the swift-corelibs-foundation tests pass. Now I am seeing the following test failure for swift-corelibs-xctest:
|
Please test with following pull request: @swift-ci test linux |
@swift-ci clean test |
Build failed |
I think @adrian-prantl address the |
@swift-ci test macOS |
Build failed |
I am seeing new test failures that appear unrelated. Looks like new breakage on |
All the linux bots are failing with |
@shajrawi You need a clean build to get rid of it |
@shajrawi yeah sorry about that; apparently changing the version in the build-script doesn't reflect as a build dependency. I've triggered the bots to clean their workspaces. |
AFAIK, this is an inherent limitation of CMake. Once configuration parameters are cached, they can only be reset by removing the CMake cache. |
Maybe we shouldn't be marking that variable as "CACHE"? |
rdar://problem/31899950