[swift-dev] [Swift CI] Build Failure: OSS - Swift Package - OS X (master) #765

Title: Report [FAILURE] oss-swift-package-osx [#765] Build URL:https://ci.swift.org/job/oss-swift-package-osx/765/ Project:oss-swift-package-osx Date of build:Tue, 28 Nov 2017 20:48:21 -0600 Build duration:3 hr 7 min Identified problems:Compile Error: This build failed

[swift-dev] Swift Incremental broken

The incremental OS X bot is broken. Anyone has any ideas? Thanks! https://ci.swift.org/job/oss-swift-incremental-RA-osx/1586/ FAILURE EXECUTING SUBPROCESS command:

Re: [swift-dev] Default deployment target for swiftc

+1 -Chris > On Nov 28, 2017, at 10:36 AM, Tony Allevato via swift-dev > wrote: > > I agree, the currently running OS seems like the right default here. > Progressive disclosure and ease of prototyping are good motivations here. If > I just want to quickly prototype

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 16.10 (swift 4.1) #281

On Tue, Nov 28, 2017 at 3:57 PM, Mishal Shah via swift-dev < swift-dev@swift.org> wrote: > :0: error: module map file > '/home/buildnode/jenkins/workspace/oss-swift-4.1-incremental-RA-linux-ubuntu-16_10/swift-corelibs-libdispatch/dispatch/module.modulemap' > not found:0: error: module map file

Re: [swift-dev] Potential contributions to compilation time reporting?

> On Nov 28, 2017, at 5:01 PM, Mark Lacey via swift-dev > wrote: > > > >> On Nov 19, 2017, at 9:02 PM, Brian Gesiak via swift-dev > > wrote: >> >> Thanks for the reply, Graydon, and for your other email on the topic

Re: [swift-dev] Potential contributions to compilation time reporting?

> On Nov 19, 2017, at 9:02 PM, Brian Gesiak via swift-dev > wrote: > > Thanks for the reply, Graydon, and for your other email on the topic > ! > > I need to take more time to look into some

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 16.10 (swift 4.1) #281

:0: error: module map file '/home/buildnode/jenkins/workspace/oss-swift-4.1-incremental-RA-linux-ubuntu-16_10/swift-corelibs-libdispatch/dispatch/module.modulemap' not found <>:0: error: module map file

[swift-dev] Update: Moving to Discourse

Hi All- I just wanted to update you all on our migration to Discourse. We are well on our way, with a prototype server and initial import of mailing list data completed! As part of the move to Discourse, we have the opportunity to do some re-organization to help foster communication and

Re: [swift-corelibs-dev] Status of DispatchQueue.concurrentPerform on Linux?

For what it's worth, I've been using DispatchQueue.concurrentPerform on my own projects that run on both Darwin and Linux and it's worked well for both. I haven't noticed the issue you're describing. Perhaps you could include a repro case that demonstrates this behavior? PS: However, my Swift

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 16.04 (master) #762

module map file '/home/buildnode/jenkins/workspace/oss-swift-package-linux-ubuntu-16_04/swift-corelibs-libdispatch/dispatch/module.modulemap' not found Those usually go away after a clean build? > On Nov 28, 2017, at 1:10 PM, no-re...@swift.org wrote: > > [FAILURE]

Re: [swift-dev] [swift-users] Where to read about *.swiftmodule file format?

Hi Volodymyr, The format is not documented anywhere and is subject to change. A good starting point is include/swift/Serialization/ModuleFormat.h, but I would first be curious to know what exactly you’re planning on doing with it. It might be better to extend swift-ide-test and similar

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

Doesn't look like any of us. Anything happen over in Dispatch-land? :0: error: cannot open file '/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-16_10/swift-corelibs-libdispatch/private/module.modulemap': No such file or directory Jordan > On Nov 28, 2017, at 11:57,

Re: [swift-dev] Default deployment target for swiftc

There should not be any availability checks required in the common fast-prototyping case, where your SDK version and your running OS version are the same. Availability checks are required when some API has changed since the OS version that is your deployment target. In the fast-prototyping

Re: [swift-dev] Default deployment target for swiftc

Thanks, all. Sounds like following Clang and the interpreter is the way to go. https://github.com/apple/swift/pull/13114 Jordan > On Nov 27, 2017, at 16:44, Jordan Rose via swift-dev > wrote: > > Hi, all. Consider the following command, as run on a Mac with an

Re: [swift-dev] Default deployment target for swiftc

I think you'll still have to write the availability checks, because Swift will make you. I think the fixit also tells you what you need for the API you're trying to use. The confusing thing will be, though, that it'll use the fall-back path unless you explicitly set the target version. > On

Re: [swift-dev] Default deployment target for swiftc

I agree, the currently running OS seems like the right default here. Progressive disclosure and ease of prototyping are good motivations here. If I just want to quickly prototype something, I'm not going to be thinking about choosing a minimum OS; I'm just going to write something using the APIs

Re: [swift-corelibs-dev] Better integration with UNIX tools

+1 from me. I ended up making a wrapper objc->swift around system() since it was removed from swift recently, however, it behaves (from a user standpoint) exactly how I’d like. If my command line util jumps out to another program and it needs stdin/out/err, it all just passes through which is

Re: [swift-corelibs-dev] Better integration with UNIX tools

Why does it imply a run loop rather than one of many multithreading possibilities (dispatch queue, starting one more thread, etc)? And even if it did use run loops, why is that a problem? In general we have been discouraging the use of synchronous and blocking API for many years now. It’s

[swift-dev] [Swift CI] Build Still Failing: 1. OSS - Swift (Tools Opt+Assert, Stdlib Opt+DebInfo+Assert, Resilience) - macOS (master) #119

New issue found!Title: Report [FAILURE] oss-swift_tools-RA_stdlib-RDA_test-macos-resilience [#119] Build URL:https://ci.swift.org/job/oss-swift_tools-RA_stdlib-RDA_test-macos-resilience/119/ Project:oss-swift_tools-RA_stdlib-RDA_test-macos-resilience Date of build:Tue, 28