this may be an unintended consequence of us putting the Linux overlay into the
library repo (as opposed to the compiler repo).
I still think that is the right place for the overlay to live though, and that
we should move the Darwin overlay there as well medium term (and work out any
resulting b
looks like a libkqueue test failed
dave / hubertus may have seen this before ?
make check-TESTS
make[2]: Entering directory
`/home/buildnode/disk2/workspace/oss-swift-incremental-RA-libdispatch-linux-ubuntu-14_04/Ninja-ReleaseAssert/libdispatch-linux-x86_64/libkqueue'
make[3]: Entering director
> On Dec 17, 2015, at 21:16, Daniel A. Steffen via swift-corelibs-dev
> wrote:
>
>>
>> On Dec 17, 2015, at 13:41, Pierre Habouzit via swift-corelibs-dev
>> wrote:
>>
>>
>> -Pierre
>>
>>> On Dec 17, 2015, at 1:35 PM, Pierre H
> On Dec 17, 2015, at 13:41, Pierre Habouzit via swift-corelibs-dev
> wrote:
>
>
> -Pierre
>
>> On Dec 17, 2015, at 1:35 PM, Pierre Habouzit wrote:
>>
>>> On Dec 17, 2015, at 12:40 PM, Tony Parker via swift-corelibs-dev
>>> wrote:
>>>
>>> Hi Dzianis,
>>>
On Dec 17, 2015, at 12:36 P
