Re: [swift-dev] JIRA labels (no worries)

> On May 27, 2016, at 10:05 AM, Brian Gesiak via swift-dev > wrote: > > Hey Jordan, > > Thanks for the email! Very good point -- and I definitely felt weird > assigning "Swift 3" labels to tasks, considering it's not up to me to decide > what goes into Swift 3 or not. Still, I think it's hel

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

Mine, fixed in 130d352. - Daniel > On May 27, 2016, at 3:39 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-linux-ubuntu-15_10 [#5339] > > Build URL: > https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/5339/ >

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

That is worrisome, it is possible this is a non-deterministic failure as I made some changes to remove a sleep which _should_ be unnecessary from the test. I filed: Non-deterministic test failure with source file changing to investigate. - Daniel > On May 27, 2016, at 3:09 PM, Jordan Rose

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

Ah, my bad, the next build passed cleanly. Jordan > On May 27, 2016, at 15:08, Jordan Rose wrote: > > [+swift-build-dev] Doesn't look like any of these changes would have affected > the package manager. Maybe the blamelist is missing something? > > /Users/buildnode/jenkins/workspace/oss-swift

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

[+swift-build-dev] Doesn't look like any of these changes would have affected the package manager. Maybe the blamelist is missing something? /Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx/swiftpm/Tests/Functional/MiscellaneousTests.swift:285: error: -[FunctionalTestSuite.Miscell

Re: [swift-dev] SwiftGlibc: Use VFS overlay instead of -fmodule-map-file

I’m not sure if we could dynamically generate the YAML because of multiarch, and because the GCC triple isn’t always the same as the LLVM triple. For example, you might built ‘armv7-linux-gnueabihf’ for Swift/LLVM, but GCC only has ‘arm-linux-gnueabihf’. But yeah, thats a really good find, it’

Re: [swift-dev] [Swift CI] Build Still Failing: OSS - Swift Package - Ubuntu 15.10 (master) #1407

This failure makes it look like the binaries we build no longer are capable of finding their runtime libraries: -- Command 7: "/tmp/swift-integration-tests/test-xctest-package/Output/test-xctest-package.py.tmp.dir/tool/.build/debug/tool" Command 7 Result: 127 Command 7 Output: None Command 7 Std

Re: [swift-dev] JIRA labels (no worries)

Hey Jordan, Thanks for the email! Very good point -- and I definitely felt weird assigning "Swift 3" labels to tasks, considering it's not up to me to decide what goes into Swift 3 or not. Still, I think it's helpful to see, at a glance, what are the time-sensitive tasks for a given project. Ideal

Re: [swift-dev] SwiftGlibc: Use VFS overlay instead of -fmodule-map-file

> Neat! The problem is almost certainly that “//usr” is also a net name, so it would be treated as a single path component by llvm’s path handling code. We would need to explicitly add some fallback case to handle this. Worth a bug report! > > We certainly are not just doing exact string matches a

Re: [swift-dev] Swift closure memory problem

Hi Alon, > On 27 May 2016, at 09:01, Alon Muroch via swift-dev > wrote: > > Hi everyone ! > Its my first time writing here so i hope i could contribute. Your question would be more appropriate for the swift-users list. This list is mainly for developers of the Swift toolchain (e.g. the swif

[swift-dev] Swift closure memory problem

Hi everyone ! Its my first time writing here so i hope i could contribute. The following code seems to create a retain cycle that doesn't let SomeClass1 to release. Am i missing something ? ​​Alon. ___ swift-dev mailing list swift-dev@swift.org https:/