From: Zack Weinberg <zackw@panix.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Siddhesh Poyarekar <siddhesh@gotplt.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v3 2/2] posix: Implement preadv2 and pwritev2
Date: Fri, 02 Jun 2017 13:04:00 -0000 [thread overview]
Message-ID: <CAKCAbMi95KU=kO1vyj7O4GpHFngOpjDGxCog83nnaYjrRwOF4Q@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOpu=yRUr=bHE=h2CJA7e0=U8qz5g5M_PL3GKAtLoUmmJA@mail.gmail.com>
On Fri, Jun 2, 2017 at 9:00 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
>
> I got
>
> [hjl@gnu-tools-1 build-x86_64-linux]$ ./misc/tst-preadvwritev2
> error: tst-preadvwritev-common.c:74: first pwritev returned -1
> error: 1 test failures
> [hjl@gnu-tools-1 build-x86_64-linux]$
>
> on one of my x86-64 machines. But when I ran it under gdb, it passed.
I see this as well, for both tst-preadvwritev2 and
tst-preadvwritev64v2 on my x86-64 machine (kernel 4.9). Like HJ, if I
run the test manually, it succeeds.
(And apart for everything else, that error message needs to be fixed
to print strerror(errno).)
zw
next prev parent reply other threads:[~2017-06-02 13:04 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 12:43 [PATCH v2 1/2] manual: Add preadv and pwritev documentation Adhemerval Zanella
2017-05-04 12:43 ` [PATCH v3 2/2] posix: Implement preadv2 and pwritev2 Adhemerval Zanella
2017-05-11 19:02 ` Adhemerval Zanella
2017-05-30 14:19 ` Adhemerval Zanella
2017-05-31 18:51 ` Adhemerval Zanella
2017-06-01 16:40 ` Siddhesh Poyarekar
2017-06-01 18:14 ` Adhemerval Zanella
2017-06-02 13:00 ` H.J. Lu
2017-06-02 13:04 ` Zack Weinberg [this message]
2017-06-02 13:34 ` Florian Weimer
2017-06-02 14:07 ` Adhemerval Zanella
2017-06-02 14:22 ` Zack Weinberg
2017-06-02 18:20 ` Adhemerval Zanella
2017-06-02 19:02 ` Florian Weimer
2017-06-02 19:46 ` Adhemerval Zanella
2017-06-03 1:47 ` H.J. Lu
2017-06-03 8:22 ` Andreas Schwab
2017-06-03 11:04 ` H.J. Lu
2017-06-03 11:23 ` Florian Weimer
2017-06-03 11:27 ` H.J. Lu
2017-06-03 11:29 ` H.J. Lu
2017-06-03 12:52 ` Andreas Schwab
2017-06-03 12:57 ` H.J. Lu
2017-06-03 13:48 ` Zack Weinberg
2017-06-03 13:52 ` H.J. Lu
2017-06-03 13:58 ` Zack Weinberg
2017-06-03 14:16 ` H.J. Lu
2017-06-03 15:28 ` Andreas Schwab
2017-06-04 13:42 ` H.J. Lu
2017-06-04 15:03 ` Zack Weinberg
2017-06-05 13:37 ` Adhemerval Zanella
2017-06-02 13:04 ` Tulio Magno Quites Machado Filho
2017-06-02 14:04 ` Adhemerval Zanella
2017-05-04 12:51 ` [PATCH v2 1/2] manual: Add preadv and pwritev documentation Florian Weimer
2017-05-04 13:47 ` Adhemerval Zanella
2017-05-04 18:46 ` Adhemerval Zanella
2017-05-04 18:46 ` Florian Weimer
2017-05-04 18:53 ` Adhemerval Zanella
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKCAbMi95KU=kO1vyj7O4GpHFngOpjDGxCog83nnaYjrRwOF4Q@mail.gmail.com' \
--to=zackw@panix.com \
--cc=adhemerval.zanella@linaro.org \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).