Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #3902

94c85b26b1 fixes this. - Joe > On May 6, 2016, at 10:51 PM, Joe Pamer via swift-dev > wrote: > > Taking a look now. > > - Joe > >> On May 6, 2016, at 10:33 PM, no-re...@swift.org >> wrote: >> >> [FAILURE] oss-swift-incremental-RA-osx [#3902] >> >> Build URL:

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #3902

Taking a look now. - Joe > On May 6, 2016, at 10:33 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-osx [#3902] > > Build URL:https://ci.swift.org/job/oss-swift-incremental-RA-osx/3902/ > > Project: oss

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 14.04 (master) #4613

TypeName.swift failure fixed in 6e423a0. -Chris > On May 6, 2016, at 9:33 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-linux-ubuntu-14_04 [#4613] > > Build URL: > https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-14_04/4613/ >

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #3898

Fixed in 684e660. -Chris > On May 6, 2016, at 9:30 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-osx [#3898] > > Build URL:https://ci.swift.org/job/oss-swift-incremental-RA-osx/3898/ > > Project: oss-

[swift-dev] Swift 3.0 release process

Hi everyone, I just posted the branching and release process for Swift 3.0: https://swift.org/blog/swift-3-0-release-process/ Please take a read and let me know if there are any questions. Cheers, Ted

Re: [swift-dev] [SR-710][RFC] Automatically detecting XCTest test methods on Linux: Reflection? SourceKit?

Sorry for the delay in following up. I have had several long discussions on this topic with Dmitri and others, which I will try to summarize here: *TL;DR*: We think the right long-term path forward is to pursue porting SourceKit to Linux, and would like to explore that direction first before tryi

Re: [swift-dev] swift (ABI) and Windows

On Thu, May 5, 2016 at 5:26 PM, Joe Groff via swift-dev wrote: > > > On May 5, 2016, at 4:18 PM, Sangjin Han via swift-dev < > swift-dev@swift.org> wrote: > > > > Hi, > > > > I made an experimental MSVC port. Of cause, dllimport/dllexport and the > driver for linking and many other part is not im

Re: [swift-dev] Why are we re-linking?

Is it so much work to move the data out of line (as Chris suggested) that we shouldn't just do that and involve another "mode"? - Daniel > On May 6, 2016, at 9:23 AM, Dmitri Gribenko via swift-dev > wrote: > > On Fri, May 6, 2016 at 9:16 AM, Jordan Rose wrote: >> Hm. That might be a nice ba

Re: [swift-dev] Why are we re-linking?

On Fri, May 6, 2016 at 9:16 AM, Jordan Rose wrote: > Hm. That might be a nice balance, and it’s not entirely a lie: that’s the > version of the compiler that you’re using, if not the stdlib and runtime. > I’d still like to put it behind a flag, so that we can turn it off it > certain configuration

Re: [swift-dev] Why are we re-linking?

> On May 6, 2016, at 09:23, Dmitri Gribenko wrote: > > On Fri, May 6, 2016 at 9:16 AM, Jordan Rose wrote: >> Hm. That might be a nice balance, and it’s not entirely a lie: that’s the >> version of the compiler that you’re using, if not the stdlib and runtime. >> I’d still like to put it behind

Re: [swift-dev] Why are we re-linking?

Hm. That might be a nice balance, and it’s not entirely a lie: that’s the version of the compiler that you’re using, if not the stdlib and runtime. I’d still like to put it behind a flag, so that we can turn it off it certain configurations, like #2105