(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-suite.log).
Two questions:
1. Can someone help me decipher that log to figure out what is going
wrong?
2. It tells me to report the errors to libdispatch@macosforge.org. Is
that something I really should do?
The three failures:
dispatch_select:
dispatch_io
dispatch_io_net
most likely occur because you don't have a /usr/share/dict/words file,
which you can get by installing something like the wamerican or wbritish
backage.
<swift-corelibs-dev@swift.org>
···
From: Ryan Lovelett via swift-corelibs-dev
To: swift-corelibs-dev@swift.org
Date: 13/08/2016 22:11
Subject: [swift-corelibs-dev] libdispatch Arch Linux
Sent by: swift-corelibs-dev-bounces@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 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-suite.log).
Two questions:
1. Can someone help me decipher that log to figure out what is going
wrong?
2. It tells me to report the errors to libdispatch@macosforge.org. Is
that something I really should do?
[attachment "test-suite.log" deleted by Chris Bailey/UK/IBM]
_______________________________________________
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
On Sun, Aug 14, 2016, at 07:59 AM, Chris Bailey wrote:
Hi Ryan:
The three failures:
dispatch_select:
dispatch_io
dispatch_io_net
most likely occur because you don't have a /usr/share/dict/words file,
which you can get by installing something like the wamerican or
wbritish backage.
From: Ryan Lovelett via swift-corelibs-dev <swift-corelibs-
dev@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-bounces@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 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-suite.log).
Two questions:
1. Can someone help me decipher that log to figure out what is going
wrong?
2. It tells me to report the errors to libdispatch@macosforge.org. Is
that something I really should do? [attachment "test-suite.log"
deleted by Chris Bailey/UK/IBM]
_______________________________________________ swift-corelibs-dev
mailing list swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
The test that is failing creates a temporary directory, sets it to be
read-only, and then attempts to write into the directory. It is expecting
the write to fail with errno value EACESS (13). Instead, the write attempt
is succeeding (errno is 0).
I'd guess that either you are running the test as root/sudo or the
chmod operation on the temporary directory to make it read-only failed.
--dave
[BEGIN] error from write to write protected directory
Actual: 0
Expected: 13 Permission denied
[FAIL] error from write to write protected directory (dispatch_io.c:611)
dispatch_io.c:611
···
Ryan Lovelett <swift-dev@ryan.lovelett.me> 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.
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 <swift-dev@ryan.lovelett.me> 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. It is
expecting the write to fail with errno value EACESS (13). Instead,
the write attempt is succeeding (errno is 0).
I'd guess that either you are running the test as root/sudo or the
chmod operation on the temporary directory to make it read-only
failed.
--dave
[BEGIN] error from write to write protected directory
Actual: 0
Expected: 13 Permission denied
[FAIL] error from write to write protected directory
(dispatch_io.c:611)
dispatch_io.c:611
