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

2016-10-14 Thread Daniel Dunbar via swift-dev
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

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

2016-10-14 Thread Doug Coleman via swift-dev
POSIX.popen() sometimes breaks the build Looks like it’s still broken? Doug > On Oct 14, 2016, at 5:17 PM, Doug Coleman wrote: > > Flaky test code for popen()? I think we saw this before... > > > fatal error: 'try!' expression unexpectedly raised an error: >

[swift-dev] Ubuntu 16.10 Bots on ci.swift.org

2016-10-14 Thread mishal_shah via swift-dev
Ubuntu 16.10 support added to ci.swift.org ! Ubuntu 16.10 toolchains will be available on swift.org. Master: 0. OSS - Swift Incremental RA - Ubuntu 16.10 (master) 0. OSS - Swift Incremental RA -

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

2016-10-14 Thread Doug Coleman via swift-dev
Flaky test code for popen()? I think we saw this before... fatal error: 'try!' expression unexpectedly raised an error: POSIX.ShellError.popen(arguments: ["echo", "foo"], close error: Unknown error -1): file

Re: [swift-dev] builtin command for invoking a subset of the tests

2016-10-14 Thread Alexis Beingessner via swift-dev
I've filed https://bugs.swift.org/browse/SR-2960 https://bugs.swift.org/browse/SR-2961 (I have no idea of I've done that right) Sent from my iPhone > On Oct 14, 2016, at 1:01 PM, Tony Parker wrote: > > >> On Oct 14, 2016, at 9:54 AM, Alexis

Re: [swift-dev] [semantic-arc][proposal] High Level ARC Memory Operations

2016-10-14 Thread Andrew Trick via swift-dev
This seems fine to me… at a high level! -Andy > On Oct 14, 2016, at 2:44 PM, Michael Gottesman via swift-dev > wrote: > > Attached below is a final version of the proposal. I am going to commit it to > the repo if there are no further questions/changes/etc. > >>

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

2016-10-14 Thread mishal_shah via swift-dev
Hi, Can someone please look at this error? Test Case 'ShellTests.testPopen' started at 23:47:15.353 fatal error: 'try!' expression unexpectedly raised an error: POSIX.ShellError.popen(arguments: ["echo", "foo"], close error: Unknown error -1): file

Re: [swift-dev] [semantic-arc][proposal] High Level ARC Memory Operations

2016-10-14 Thread Michael Gottesman via swift-dev
Attached below is a final version of the proposal. I am going to commit it to the repo if there are no further questions/changes/etc. > https://gottesmm.github.io/proposals/high-level-arc-memory-operations.html >

Re: [swift-dev] Dictionary Collision Resolution Guarantees

2016-10-14 Thread Dave Abrahams via swift-dev
on Fri Oct 14 2016, Ole Begemann wrote: > On 14/10/2016 02:46, Dave Abrahams wrote: > >>> OK cool, is there any reason it’s even written down? I don’t see any code >>> that’s obviously relying on it. (seems fine to delete it?) >> >> It's written down because we've never formalized our index

Re: [swift-dev] builtin command for invoking a subset of the tests

2016-10-14 Thread Tony Parker via swift-dev
Hi Alexis, In fact there is already a script which is closer to what you want, in swift/utils/run-test. It could probably use some additional love and attention to be a bit more usable (for example, printing out the help if you invoke it with no arguments), but I use it all the time. - Tony

[swift-dev] builtin command for invoking a subset of the tests

2016-10-14 Thread Alexis via swift-dev
When fixing tests, it’s often useful to be able to run some subset of them, usually based on some pattern. From my searching, the recommended way to do this seems to be to directly invoke `lit.py`. Doing this by hand is tedious, so I use the following script: #!/bin/bash