That seems about right. The tests run in a chroot, where the script is
root, to ensure that I control dependencies and such.
Not sure what I I can do about this test. 🤔
Thanks for the help Dave!
On Mon, Aug 15, 2016, at 10:57 AM, David P Grove wrote:
> Ryan Lovelett wrote on 08/14/2016
> 05:10:
Ryan Lovelett wrote on 08/14/2016 05:10:34 PM:
>
> However, the `dispatch_io` test is still failing. I've added the
> test-suite.log once more.
>
Hi Ryan,
The test that is failing creates a temporary directory, sets it to be
read-only, and then attempts to write into the directory. I
n Lovelett via swift-corelibs-dev d...@swift.org>
> To:swift-corelibs-dev@swift.org
> Date:13/08/2016 22:11
> Subject:[swift-corelibs-dev] libdispatch Arch Linux
> Sent by:swift-corelibs-dev-boun...@swift.org
>
>
>
> (I know that this is
swift-corelibs-dev@swift.org
Date: 13/08/2016 22:11
Subject:[swift-corelibs-dev] libdispatch Arch Linux
Sent by:swift-corelibs-dev-boun...@swift.org
(I know that this is not 100% expected to work yet. AND I'm working on
an unsupported distro... but I thought I'd a
(I know that this is not 100% expected to work yet. AND I'm working on
an unsupported distro... but I thought I'd ask).
Trying to build libdispatch on Linux (Arch Linux 4.6.4-1-ARCH). The
build seems to go fine up until the tests. At this point there are 3
failing tests (see the attached test-suit
