From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: DJ Delorie <dj@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v3] i386: Use pthread_barrier for synchronization on tst-bz21269
Date: Mon, 15 May 2023 15:33:19 -0300 [thread overview]
Message-ID: <5a3f6747-c39e-506e-eccd-88d71a6418f9@linaro.org> (raw)
In-Reply-To: <xnsfc3c1qr.fsf@greed.delorie.com>
On 10/05/23 18:31, DJ Delorie wrote:
>
> Adhemerval Zanella Netto <adhemerval.zanella@linaro.org> writes:
>> On 02/03/23 17:21, DJ Delorie wrote:
>>> I'm not opposed to removing it. Even with the fixed I put in, the test
>>> is still more likely to fault "for some reason" than for the expected
>>> reason.
>>>
>>
>> Ok, this LGTM then. The patchwork false positive failures is being really
>> annoying.
>
> We dropped the ball on this one. We ended up with three options:
>
> 1> Adhemerval's v4 patch
> https://sourceware.org/pipermail/libc-alpha/2023-February/145934.html
> 2> DJ's v3 patch
> https://sourceware.org/pipermail/libc-alpha/2023-March/145999.html
> 3> remove the test
>
> Which option were you agreeing to, and do you still agree to it?
>
Either 2 or 3 is fine for me, since I acked your patch I think we can
go with 2 for now.
next prev parent reply other threads:[~2023-05-15 18:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 16:15 Adhemerval Zanella
2023-02-27 22:21 ` DJ Delorie
2023-02-28 14:29 ` Adhemerval Zanella Netto
2023-03-02 5:10 ` DJ Delorie
2023-03-02 17:00 ` Adhemerval Zanella Netto
2023-03-02 20:21 ` DJ Delorie
2023-03-08 18:01 ` Adhemerval Zanella Netto
2023-05-10 21:31 ` DJ Delorie
2023-05-15 18:33 ` Adhemerval Zanella Netto [this message]
2023-05-16 19:10 ` DJ Delorie
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=5a3f6747-c39e-506e-eccd-88d71a6418f9@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.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).