Re: [swift-dev] I can't install swift on ubuntu 14.04 lts

What specific problem do you encounter? Please include logs from the command line and the steps you followed. - Daniel > On Dec 6, 2015, at 8:16 AM, Piero Sabino via swift-dev > wrote: > > I can't install swift on ubuntu 14.04 lts following the instructions on > "www.swift.org". > > __

Re: [swift-dev] Reducing the size of Swift binaries by shortening symbols

Hi Nadav, One thing you didn't call out here was any connection to visibility. I would expect that in practice it is quite common for most of the symbols to not be visible outside the linkage unit. Inside the linkage unit, the compiler can already rename many of the symbols in any way it likes.

Re: [swift-dev] Reducing the size of Swift binaries by shortening symbols

> On Dec 20, 2015, at 11:26 PM, Nadav Rotem wrote: > > >> On Dec 20, 2015, at 1:01 PM, Daniel Dunbar > > wrote: >> >> Hi Nadav, > > Hi Daniel, > >> >> One thing you didn't call out here was any connection to visibility. > > This is a great point! > > Apps

Re: [swift-dev] Official Docker Image & "Blessing"s of Community Platforms

Hi Thomas, Just a question: how would the constant changing of the Swift compiler version and language interact with this? It seems odd to have an "official" version of what is an otherwise unreleased language version/compiler. - Daniel > On Dec 29, 2015, at 10:07 AM, Thomas Catterall via swi

Re: [swift-dev] [FAILURE] Swift Linux Package (Ubuntu 15.10) [#885]

+Max > On Apr 3, 2016, at 1:20 PM, Mishal Shah via swift-dev > wrote: > > Hi, > > Linux package bots started failing after these commits, which is causing pull > request testing to fail. > > Thanks, > Mishal Shah > [FAILURE] oss-swift-package-linux-ubuntu-15_10 [#885] > > Build URL: >

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

> On Apr 3, 2016, at 3:36 PM, Dmitri Gribenko wrote: > > On Sun, Apr 3, 2016 at 2:11 PM, Brian Gesiak wrote: >> I think #2 is the best option. It’s less work than both #1 and #3. I believe >> logic like IsTestCandidate belongs in libIDE anyway—SourceKit should stick >> to XPC and asynchronous c

Re: [swift-dev] [FAILURE] Swift Linux Package (Ubuntu 15.10) [#885]

If you clone the repo I believe it has a README which describes how to run them. - Daniel > On Apr 4, 2016, at 11:07 AM, Max Howell wrote: > > Failing in the integration tests. > > Seemingly these don’t run for SwiftPM CI ? > > I’m not 100% sure how to run them locally even. > >> +Max >> >

Re: [swift-dev] Swiftpm CI failure on OSX due to watchkit

Mishal, do you know what is going on here? - Daniel > On Apr 5, 2016, at 10:22 AM, Ankit Agarwal via swift-dev > wrote: > > Hi, > > https://github.com/apple/swift-package-manager/pull/219 > has failed OSX CI > twice due to what seem

Re: [swift-dev] quick, spot the UB in this code:

Could we get a method that takes a [UInt8] directly and performs the same basic function? In my experience I have frequently wanted such a thing (primarily when debugging things) when working with binary protocols that have embedded ASCII data. - Daniel > On Apr 6, 2016, at 9:51 PM, Dmitri Gr

Re: [swift-dev] quick, spot the UB in this code:

> On Apr 6, 2016, at 9:58 PM, Dmitri Gribenko wrote: > > On Wed, Apr 6, 2016 at 9:54 PM, Daniel Dunbar wrote: >> Could we get a method that takes a [UInt8] directly and performs the same >> basic function? > > I think the root of the surprise here is that the compiler converts > [UInt8] into

Re: [swift-dev] Building Toolchain Fails

I believe this was a transient failure on trunk, please update and retry. - Daniel > On Apr 7, 2016, at 10:19 AM, Daniel Eggert via swift-dev > wrote: > > I'm seeing this when trying to build a toolchain off master: > > % ./utils/update-checkout --clone-with-ssh > % caffeinate ./utils/build-

Re: [swift-dev] Swift modules aware of their version tag on compilation

Have you seen: https://github.com/apple/swift-package-manager/pull/122 Also, please consider starting a new thread instead of replying to the digest email (which is very large, and confusing since it includes many topics). - Daniel >

[swift-dev] test-repl-glibc failure

What is the status of the Ubuntu packages CI failure: swift-package-tests :: repl/test-repl-glibc.py It has been failing for a while now and I would like to get back to being able to use @swift-ci please test and merge. - Daniel ___ swift-dev ma

[swift-dev] Including `FileCheck` in downloadable toolchains

Hi all, I would like to propose that we include `FileCheck` in the downloadable toolchains. The downloadable toolchains are quite useful for people who are wanting to work on Swift projects that use FileCheck (llbuild, swift-integration-tests), but don't want to build everything from scratch.

Re: [swift-dev] test-repl-glibc failure

pr 21, 2016, at 9:20 PM, Daniel Dunbar via swift-dev >> mailto:swift-dev@swift.org>> wrote: >> >> What is the status of the Ubuntu packages CI failure: >> swift-package-tests :: repl/test-repl-glibc.py >> >> It has been failing for a while now and I wo

Re: [swift-dev] Swift incremental compile profiling

> On Apr 24, 2016, at 3:19 PM, Samantha John via swift-dev > wrote: > > Hello List (cc/Jordan), > > At a high level: Brian and I are looking into contributing to incremental > compilation in Swift. Right now we're trying to do an incremental compile by > invoking swiftc. > > Our understa

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

Mishal, I believe this failed because this builder doesn't have the swiftpm source checked out, even though it does for Linux (and the @swift-ci test builders do, apparently). Can you update the Jenkins config to also checkout out the OSS apple/swift-package-manager? I will revert in the meanti

Re: [swift-dev] Swift incremental compile profiling

> On Apr 25, 2016, at 8:15 PM, Samantha John wrote: > > On Mon, Apr 25, 2016 at 12:11 AM, Daniel Dunbar > wrote: > >> On Apr 24, 2016, at 3:19 PM, Samantha John via swift-dev >> mailto:swift-dev@swift.org>> wrote: >> >> Hello List (cc/Jordan), >> >> At a hi

Re: [swift-dev] hmap files

They are "header map" files and you are right they are very poorly documented. Xcode uses them to provide the compiler with a mapping of textual include names to actual file paths. What are you specifically looking into? - Daniel > On Apr 26, 2016, at 11:42 AM, Rafkind, Jon via swift-dev >

Re: [swift-dev] hmap files

Yes, you should avoid passing header map files. They should only be used when trying to integrate with existing Xcode projects, when invoking swiftc yourself you should use the simpler header search path options (-I, -F). - Daniel > On Apr 26, 2016, at 11:51 AM, Rafkind, Jon wrote: > > Well

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

-- Test Suite 'All tests' started at 18:01:00.742 Test Suite 'TestFoundation.xctest' started at 18:01:00.745 Test Suite 'TestNSAffineTransform' started at 18:01:00.745 /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-15_10-long-test/swift/utils/build-script-impl: line 2029:

Re: [swift-dev] [swift-users] Swift Package Manager and main.swift

My preference here is that SwiftPM treat "Main.swift" as an error (and suggest "main.swift"), for now. If we agree the compiler should support it as a synonym for main.swift, then we can remove that. - Daniel > On May 2, 2016, at 10:55 AM, Jordan Rose via swift-dev > wrote: > > If it were j

Re: [swift-dev] Using locally built toolchain in Xcode

The other thing needed is to put it somewhere Xcode will find it, either in the system Library or the user local Library Toolchains directory. I personally do this by having a symlink from: ~/Library/Developer/Toolchains/swift-dev.xctoolchain to a version I build up with Swift (with an Info.pli

Re: [swift-dev] Building SwiftPM with Foundation

What you will need to do to make this work is to get the "fake toolchain" to look like how an actual toolchain looks on disk (e.g., libFoundation in the same relative position, in `/../lib/swift/linux`), presumably using a symlink. The special rpath is what is causing the built swift-build (in t

[swift-dev] Linux test failure

Anyone know what is up with this Linux test failure? We keep seeing it block @swift-ci merges: Failing Tests (1): Swift :: compiler_crashers/28279-swift-archetypebuilder-potentialarchetype-getnestedtype.swift - Daniel ___ swift-dev mailing list s

Re: [swift-dev] Linux test failure

Awesome, thanks! - Daniel > On May 5, 2016, at 4:17 PM, Mark Lacey wrote: > > >> On May 5, 2016, at 12:36 PM, Daniel Dunbar via swift-dev >> mailto:swift-dev@swift.org>> wrote: >> >> Anyone know what is up with this Linux test failure? We ke

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] [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 CI] Build Failure: OSS - Swift Package - Ubuntu 15.10 (master) #1250

I can't tell what failed here: YEAR:2016 MONTH:05 DAY:09 TOOLCHAIN_VERSION:swift-DEVELOPMENT-SNAPSHOT-2016-05-09-a ARCHIVE_DIR:swift-DEVELOPMENT-SNAPSHOT-2016-05-09-a-1229 ./clang: 9f0d189 ./llbuild: 0702f53 ./swift_integration_tests: 98f6c6d ./llvm: dffa09f ./swift: de7ef4b ./swiftpm: b26305a ./

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

+Todd This looks like lldb failures? Issue Details = ERROR: test_lldbmi_break_insert_function_pending (tools/lldb-mi/breakpoint/TestMiBreak.py) UNEXPECTED SUCCESS: test_Hc_then_Csignal_signals_correct_thread_launch_llgs (tools/lldb-server/TestLldbGdbServer.py) UNEXPECTED SUCCESS: tes

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

> On May 9, 2016, at 7:35 PM, Brian Gesiak wrote: > > Thanks for the feedback, everyone! > > Porting SourceKit to Linux seems like a reasonable solution to me. Still, > there are 354 lines of code in tools/SourceKit that reference "XPC", so a > Linux port will take more than a few lines of so

[swift-dev] Argument unused warnings

Something broke yesterday causing Swift to report gobs of argument unused warnings, see: https://bugs.swift.org/browse/SR-1546 for a reference. Does anyone know who this should go to? - Daniel ___ swift-dev mailing list swift-dev@swift.org https://

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

Mine... - Daniel > On May 17, 2016, at 5:29 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-linux-ubuntu-15_10 [#5069] > > Build URL: > https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/5069/ >

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

Hopefully fixed in 560dd6a. - Daniel > On May 17, 2016, at 5:30 PM, Daniel Dunbar via swift-dev > wrote: > > Mine... > > - Daniel > >> On May 17, 2016, at 5:29 PM, no-re...@swift.org <mailto:no-re...@swift.org> >> wrote: >> >> [FAILURE]

Re: [swift-dev] Argument unused warnings

PM, Chris Lattner wrote: > > >> On May 17, 2016, at 1:25 PM, Dmitri Gribenko via swift-dev >> wrote: >> >> On Tue, May 17, 2016 at 12:37 PM, Daniel Dunbar via swift-dev >> wrote: >>> Something broke yesterday causing Swift to report gobs

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

Foundation/NSGeometry.swift:39:25: error: value of type 'NativeType' (aka 'Double') has no member '_toBitPattern' return Int(self.native._toBitPattern()) ~^~ ~ Foundation/NSGeometry.swift:790:13: warning: result of call to 'scanUpToCharactersFromSet'

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

The failure cascade is in full effect: lit.py: lit.cfg:881: note: Using platform module dir: /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/Ninja-ReleaseAssert/swift-linux-x86_64/lib/swift/%target-sdk-name/x86_64 -- Testing: 8207 tests, 48 threads -- Testing: 0 FAI

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

cmark is failing to build: cmark: using gold linker + mkdir -p /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-15_10/Ninja-ReleaseAssert/cmark-linux-x86_64 + [[ -n '' ]] + cd /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-15_10/Ninja-ReleaseAssert/

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

FATAL: no longer a configured node for Ubuntu-14.04 java.lang.IllegalStateException : no longer a configured node for Ubuntu-14.04 at hudson.model.AbstractBuild$AbstractBuildExecution.getCurrentNode(AbstractBu

Re: [swift-dev] build-script -x freezing?

Can someone who can reproduce this issue please file a bug on bugs.swift.org with as much information as possible about what exactly is hanging? - Daniel > On May 26, 2016, at 10:53 AM, Geoffrey Wiseman via swift-dev > wrote: > > >> On May 26, 2016, at 1:20 AM, Jacob Bandes-Storch >

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] [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 - 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/ >

[swift-dev] [RFC] Toolchain based build process

Hi all, The current build process for the overall Swift project (i.e., the compiler + associated projects like Foundation, XCTest, and SwiftPM) relies on each project having dependencies on the built artifacts of previously built projects. Those dependencies are currently communicated to each p

Re: [swift-dev] [swift-build-dev] Building custom toolchain

FWIW, this: https://gist.github.com/ddunbar/598bf66952fba0e9d8aecc54995f018e is the script I currently use on OS X to get a working "swift-dev.xctoolchain" out of a built Swift. It isn't designed to work for anyone but me, but it should be easy to adapt. I always run this after every build, an

Re: [swift-dev] [swift-build-dev] Building custom toolchain

> On Jun 2, 2016, at 10:59 AM, bhargav gurlanka wrote: > > > I always run this after every build > > If I understand you correctly, you first build swift and then run this script > to create the toolchain right? > > Are you using the `build-toolchain` script to build swift? I've tried doing

Re: [swift-dev] Delaying the enforcement of ".self" out of Swift 3?

As just a user of the language, as much as I hate churn I personally wouldn't mind seeing this fixed. In this case, I think the laxness can make it harder for developers to form the right mental model of the language; I know I have personally stumbled over this in the past. - Daniel > On Jun

Re: [swift-dev] [RFC] Toolchain based build process

> On Jun 3, 2016, at 1:14 PM, Saleem Abdulrasool wrote: > > On Wed, Jun 1, 2016 at 2:18 PM, Daniel Dunbar via swift-dev > mailto:swift-dev@swift.org>> wrote: > Hi all, > > The current build process for the overall Swift project (i.e., the compiler + > assoc

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

Should be fixed in 3a4d99e. - Daniel > On Jun 8, 2016, at 8:41 PM, no-re...@swift.org wrote: > > New issue found! > > [FAILURE] oss-swift-incremental-RA-osx [#4500] > > Build URL:https://ci.swift.org/job/oss-swift-incremental-RA-osx/4500/ >

Re: [swift-dev] [swift-build-dev] [RFC] Toolchain based build process

ecause it’s more convenient to integrate with > other tools, but it’s not a big deal. Actually, I have an idea for a better > build-script argument syntax which would scale to NxM cross-compiled hosts > and targets elegantly, but that’s a topic for another day. > > Karl > > >

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

+Anders, I don't think we want the perf tests enabled in this config. - Daniel > On Jun 22, 2016, at 7:52 PM, Jordan Rose via swift-dev > wrote: > > This isn’t me. SwiftPM folks, is this real? > > /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-15_10/swiftpm/Tests/Bas

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

> On Jun 22, 2016, at 11:30 PM, Anders Bertelrud wrote: > > I'll disable it. What's the condition to check to disable it? It looks like > the other performance tests are disabled permanently, is that appropriate? It is the only option we have, currently. - Daniel > > Anders > >> On 2016

Re: [swift-dev] Bugs not reproducible on master

> On Jul 13, 2016, at 6:16 AM, Alex Hoppen via swift-dev > wrote: > > I’m currently crawling bugs.swift.org for bugs to fix and regularly encounter > bugs which I cannot reproduce on master anymore. What’s the standard protocol > for them? Close them with resolution "Can’t Reproduce" or "Done

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

Some of the prefixes are coming back. - Daniel > On Jul 15, 2016, at 10:34 AM, Anders Bertelrud via swift-dev > wrote: > > That's a surprising failure. The renaming of NSLock to Lock happened some > time ago, and AFAIK the SwiftPM side of this code hasn't changed for a long > time. > > Be

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

... and to elaborate, I am taking a look at this ... See: https://github.com/apple/swift/commit/e0ca8fbd80ace8d104eab2fe4fbf75ab107ada01 - Daniel > On Jul 15, 2016, at 10:35 AM, Daniel Dunbar wrote: > > Some of the prefixes are coming back. > > - Daniel > >> On Jul 15, 2016, at 10:34 AM,

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

Should be fixed in fa61cfe3bdae3932f90b34c414ee2c4e1967ebd3 - Daniel > On Jul 15, 2016, at 10:36 AM, Daniel Dunbar via swift-dev > wrote: > > ... and to elaborate, I am taking a look at this ... > > See: > > https://github.com/apple/swift/commit/e0ca8fbd80ace8d1

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

> On Jul 15, 2016, at 4:10 PM, Philippe Hausler via swift-dev > wrote: > > Hmm that was incomplete: > > Is there a reason why a full toolchain build didn’t pick this up? It seems > that when I built locally everything built just fine and tested ok. My > configuration that I use to test is a

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

This change has already been reverted. - Daniel > On Jul 22, 2016, at 3:02 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-package-linux-ubuntu-14_04 [#1753] > > Build URL: > https://ci.swift.org/job/oss-swift-package-linux-ubuntu-14_04/1753/ >

Re: [swift-dev] Anyone running build-toolchain on linux?

I don't run build toolchain myself (I have my own scripts for assembling one), but I run `build-script -R --llbuild --foundation --xctest -t` without issue. +Jordan, Ben for what situations could cause the actual error we are hitting there. - Daniel > On Jul 28, 2016, at 9:27 AM, Andrew Trick

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

Mine, should be fixed in 66408be65736ad2dfc314a57a00ed5b91b0b1a99. - Daniel > On Aug 11, 2016, at 12:50 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-linux-ubuntu-14_04-long-test [#693] > > Build URL: > https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-1

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

Test Case 'TestNSArray.test_sortedArrayUsingComparator' started at 01:54:49.965 TestFoundation: /home/buildnode/disk2/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/swift/include/swift/Runtime/../../../stdlib/public/SwiftShims/RefCount.h:252: bool StrongRefCount::doDecrementShouldDeallocat

[swift-dev] undefined symbol: _TFC10Foundation8NSNumberg25customPlaygroundQuickLookOs19PlaygroundQuickLook

Is anyone investigating this failure on the CI bots: -- /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-15_10/buildbot_incremental/foundation-linux-x86_64/TestFoundation/TestFoundation: symbol lookup error: /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-u

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

Anyone know who/what is tracking this: -- Testing: 19 tests, 12 threads -- FAIL: SwiftXCTestFunctionalTests :: Asynchronous/Predicates/Expectations/main.swift (10 of 19) <> TEST 'SwiftXCTestFunctionalTests :: Asynchronous/Predicates/Expectations/main.swift' FAILED **

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

Thanks Tony! - Daniel > On Aug 12, 2016, at 3:34 PM, Tony Parker wrote: > > This has been failing for too long, so I filed a JIRA and will shortly push a > commit to disable the test. > > https://bugs.swift.org/browse/SR-2332 > > - Tony > >> On Aug 1

Re: [swift-dev] [swift-build-dev] JIRA workflow: "Resolved" -> "Verify"?

Do we anticipate Verify being used in practice much? Would it be better to simplify the workflow and just have a single "Resolved/Closed/Done" state? If the originator does test the bug and find it isn't fixed, they can reopen. My guess is not that many people are going to actively look at the

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

I suspect it is just waiting on: https://github.com/apple/swift/pull/4361 to finish testing, which it looks like is close. - Daniel > On Aug 17, 2016, at 4:54 PM, Greg Parker via swift-dev > wrote: > > This is about to break all of the bots. When do you expect a fix? > >> On Aug 17, 2016,

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

IMHO you can go ahead and land the revert, it is trivial. It's unfortunate we don't have a good way to manage this yet -- my suggestion would be that when it is ready to land (again) and well tested just land both patches in mainline. I realize that is unfortunate, but it is more reliable than

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

Failing in lldb: Command invoked: /home/buildnode/jenkins/workspace/oss-swift-package-linux-ubuntu-15_10/lldb/test/dotest.py --executable /home/buildnode/jenkins/workspace/oss-swift-package-linux-ubuntu-15_10/build/buildbot_linux/lldb-linux-x86_64/bin/lldb --rerun-all-issues -C /home/buildnode

Re: [swift-dev] Llvm Toolchain packaging

Is CompatibilityVersion set in the LLVM toolchains? IIRC, Xcode 8 requires it to be 2. - Daniel > On Aug 19, 2016, at 1:12 PM, Patrice Kouame via swift-dev > wrote: > > Hi all - Xcode doesn't recognize my llvm toolchain even though it was built > right out of llvm trunk with llvm toolchain

Re: [swift-dev] [swift-lldb-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 15.10 (master) #1930

The amount of flakiness in the LLDB tests is disturbing... is there a high-level bug tracking improving this? It seems like it might be worth running a stress test of the tests on a loaded machine to try and shake out such problems. - Daniel > On Aug 19, 2016, at 1:58 PM, Todd Fiala via swift

Re: [swift-dev] [swift-lldb-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 15.10 (master) #1930

> On Aug 19, 2016, at 2:22 PM, Todd Fiala wrote: > > First off, I think the whole LLDB team can agree on the simple principle that > tests that sometimes fail is not something we’re shooting for, so we’re on > the same page with the general sentiment. > > But, rather than talking in sweeping

Re: [swift-dev] Llvm Toolchain packaging

I don't think it is documented anywhere, but it is embedded in Swift's utils/build-script-impl. - Daniel > On Aug 19, 2016, at 2:49 PM, Patrice Kouame wrote: > > Excellent! That did the trick… > > Just out of curiosity, where is that documented? The trunk llvm plist is an > old Info.plist

Re: [swift-dev] Centos 7.2 Building SwiftPM Error "error: invalid inferred toolchain"

Is `clang` available in your path? If not, this may be: https://bugs.swift.org/browse/SR-2271 - Daniel > On Aug 22, 2016, at 8:54 PM, SonWa via swift-dev wrote: > > Hi,I in Centos 7.2 run "./swift/utils/build-script --preset=buildbot_linux > installable_package=/tmp/swift.tar.gz install_de

Re: [swift-dev] __swift__

+1 - Daniel > On Aug 25, 2016, at 9:38 AM, Douglas Gregor via swift-dev > wrote: > > >> On Aug 24, 2016, at 3:57 PM, Jordan Rose > > wrote: >> >> Hey, all. I’m here to propose predefining a macro __swift__ when C code is >> compiled with Swift. We’ve gotten a

Re: [swift-dev] Building Static Binaries and Libs

> On Sep 5, 2016, at 4:13 AM, Joel Hughes via swift-dev > wrote: > > Hello, > > I hope that this is the right channel for this type of question? > > I've previously asked in swift-users about building a static binary, on > Linux, using: > > swift build -Xswiftc -static-stdlib > > It works

Re: [swift-dev] 'SwiftShims': no such file or directory

Are you building within a shared folder? We have heard reports of this happening in such an environment, but we don't have a handle on the exact steps to reproduce. Getting that information would be very useful. - Daniel > On Sep 19, 2016, at 6:53 AM, Eric Wing via swift-dev > wrote: > > I'

Re: [swift-dev] Specify Xcode command line tools when building Swift?

> On Sep 19, 2016, at 8:24 AM, Brian Gesiak via swift-dev > wrote: > > Hello all, > > I have two copies of Xcode on my development machine: > /Applications/Xcode-7.3.1.app and /Applications/Xcode.app (which is Xcode > 8.0). > > I have `Xcode > Preferences... > Locations > Command Line Tools

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

If we disable this please make sure we have a bug tracking fixing it. This seems worth investigating soon. - Daniel > On Sep 19, 2016, at 9:27 AM, Michael Gottesman wrote: > > I would appreciate it if you would do so = ). > > This is I imagine blocking @swift-ci testing. > > Michael > >> O

Re: [swift-dev] Swift Package Manager

Yes, this is intentional. We don't have a strategy yet for dealing with package-specific individual compilation flags like this. In the meantime, you can try using a system module package instead, and manually defining OPENSSL_LOAD_CONF inside a header within the system module package before y

[swift-dev] Major SwiftPM compile time regression

Swift TOT is currently taking a very long time (and upwards of 8GB) to build SwiftPM. I filed: https://bugs.swift.org/browse/SR-2754 can someone on the compiler take a look? This makes it hard to develop with TOT. - Daniel ___ swift-dev mailing list

Re: [swift-dev] [Swift CI] Build Still Failing: 0. OSS - Swift Incremental RA - Ubuntu 14.04 - Long Test (swift 3.0) #302

Alternately, we could change their build scripts to generate llbuild manifest files and build using llbuild (which tracks the Swift compiler version automatically as a dependency). This is why SwiftPM doesn't usually hit this problem, for example. - Daniel > On Sep 24, 2016, at 7:57 PM, Micha

Re: [swift-dev] Major SwiftPM compile time regression

d to the type checker (I saw Mark’s comments in the SR) > or something else? > >> On Sep 24, 2016, at 3:23 PM, Daniel Dunbar via swift-dev >> mailto:swift-dev@swift.org>> wrote: >> >> Swift TOT is currently taking a very long time (and upwards of 8GB) to buil

Re: [swift-dev] [Swift CI] Build Still Failing: 0. OSS - Swift Incremental RA - Ubuntu 14.04 - Long Test (swift 3.0) #302

> On Sep 24, 2016, at 9:33 PM, Michael Gottesman wrote: > > >> On Sep 24, 2016, at 8:15 PM, Daniel Dunbar > > wrote: >> >> Alternately, we could change their build scripts to generate llbuild >> manifest files and build using llbuild (which tracks the Swift com

Re: [swift-dev] Major SwiftPM compile time regression

>> On Sep 24, 2016, at 9:23 PM, Ted Kremenek >> <mailto:kreme...@apple.com>> wrote: >>> >>> Does this look related to the type checker (I saw Mark’s comments in the >>> SR) or something else? >>> >>>> On Sep 24, 2016

Re: [swift-dev] ccache and/or distcc for swift

Hi Oscar, Nothing exists like that for Swift yet -- it is non-trivial for several reasons, the big two are: 1. The Swift compilation model relies on global information for a module, and needs to see all the sources. This process is currently embedded in the `swiftc` driver which would need to b

Re: [swift-dev] ccache and/or distcc for swift

Ah, if you are specifically asking about the case of speeding up builds from scratch using cached results, that *is* somewhat doable, but it is still true that I don't know of an existing system for managing it for you. I want llbuild + swiftc to grow in the direction of being able to solve that

Re: [swift-dev] Validating ABI consistency between runtime C++ and standard library Swift code

Can you directly pass arguments to the function crossing the ABI boundary, and can you directly access them on the other side? If so, what you can do is simply synthesize arguments that cross the full range of the bit-representation of the argument types, and validate that you see the same range

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

Cloned off: POSIX.popen() sometimes breaks the build - Daniel > On Oct 14, 2016, at 5:25 PM, Doug Coleman via swift-dev > wrote: > > > POSIX.popen() sometimes > breaks the build > > Looks like it’s still broken? > > Doug > >> On Oct 14, 2016, at 5:17 PM, Doug Coleman >

Re: [swift-dev] Cleaning up stale branches?

While on this topic... GitHub's support for doing cross-repo pull requests is excellent. Anyone can easily fork the main repo, and push to their side repo (for example, with: `git push ddunbar HEAD:name-of-my-new-branch`) and the GitHub web UI on the main repo will automatically show you a hand

Re: [swift-dev] Cleaning up stale branches?

> On Oct 21, 2016, at 9:57 AM, Mark Lacey wrote: > > >> On Oct 21, 2016, at 9:14 AM, Daniel Dunbar via swift-dev >> mailto:swift-dev@swift.org>> wrote: >> >> While on this topic... >> >> GitHub's support for doing cross-repo pull re

Re: [swift-dev] Cleaning up stale branches?

> On Oct 21, 2016, at 12:14 PM, Dave Abrahams via swift-dev > wrote: > > > on Fri Oct 21 2016, John McCall > wrote: > >>> On Oct 21, 2016, at 10:39 AM, Dave Abrahams via swift-dev >>> wrote: >>> on Fri Oct 21 2016, Daniel Dunbar wrote: >>> While on thi

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

[xUnit] [INFO] - Processing JUnit ERROR: Step ‘Publish xUnit test result report’ aborted due to exception: java.io.IOException : remote file operation failed: /Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx at h

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

Thanks Mishal! + Mirza I reverted in: b68d158 while we investigate. - Daniel > On Dec 19, 2016, at 8:56 PM, mishal_shah via swift-dev > wrote: > > llbuild test failure: > > TEST 'llbuild-unit :: > BuildSystem/BuildSystemTests/BuildSystemFrontendTest.commandSkippingF

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

Link Get Valid decl has error type! (parameter "rhs" interface type='T._DisallowMixedSignArithmetic') 0 swift 0x03509878 1 swift 0x03509fb6 2 libpthread.so.0 0x7fbd60741670 3 libc.so.6 0x7fbd5f0847ef gsignal + 159 4 libc.so.6 0x7fbd5f

Re: [swift-dev] Fetch prebuilts of the dependencies to reduce build time

Unfortunately there is not an easy way to do this that I know of. It would be awesome if someone would build a Docker image like this and keep it up to date... - Daniel > On Dec 22, 2016, at 9:20 AM, Roberto Perez via swift-dev > wrote: > > Hi there. > > Is there a way to fetch prebuilts o

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

This is already fixed (see newer bot runs). llbuild actually does use C++14, although it's flaky on the 14.04. :) - Daniel > On Feb 10, 2017, at 9:57 AM, Jordan Rose wrote: > > Looks like an actual llbuild issue. Hey, Daniel, we're not using C++14 yet! > > /home/buildnode/disk2/workspace/oss

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

This commit can't have broken this. -- #0 0x0398af08 llvm::sys::PrintStackTrace(llvm::raw_ostream&) (/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-16_10/buildbot_incremental/swift-linux-x86_64/bin/swift+0x398af08) #1 0x0398b646 SignalHandler(int) (/home/

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 16.04 (swift 4.0) #399

On it... > On May 13, 2017, at 2:14 AM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-4.0-incremental-RA-linux-ubuntu-16_04 [#399] > > Build URL: > https://ci.swift.org/job/oss-swift-4.0-incremental-RA-linux-ubuntu-16_04/399/ >

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 16.04 (swift 4.0) #399

Should be resolved as of c386b7944cf598d56728d30a41ba3819ca04844e. - Daniel > On May 13, 2017, at 2:23 AM, Daniel Dunbar wrote: > > On it... > >> On May 13, 2017, at 2:14 AM, no-re...@swift.org >> wrote: >> >> [FAILURE] oss-swift-4.0-incremental-RA-linux-ubuntu-1

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

We have some lingering non-determinism in this test, apparently: BuildSystem/BuildSystemTests/BuildSystemTaskTests.cancelAllInQueue FAILED I'll take a look and/or disable until we get it sorted out. - Daniel > On May 17, 2017, at 10:35 AM, Michael Ilseman wrote: > > Failure in lldbuild se

  1   2   >