From: Siddhesh Poyarekar <siddhesh@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: Michael Brunnbauer <brunni@netestate.de>, libc-help@sourceware.org
Subject: Re: glibc 2.34 failed tests
Date: Wed, 4 Aug 2021 17:38:57 +0530 [thread overview]
Message-ID: <CAAmeS-ZQfa0ephHSCxgTBUd69pcE40PtXxrKDqnCBn0FWnKqXQ@mail.gmail.com> (raw)
In-Reply-To: <5f1ce02f-fa75-aa46-bd2f-16f64d210db3@linaro.org>
On Wed, Aug 4, 2021 at 5:33 PM Adhemerval Zanella
<adhemerval.zanella@linaro.org> wrote:
> On 04/08/2021 09:00, Siddhesh Poyarekar wrote:
> > On Wed, Aug 4, 2021 at 5:26 PM Adhemerval Zanella
> > <adhemerval.zanella@linaro.org> wrote:
> >>> FAIL: malloc/tst-safe-linking
> >>
> >> Siddhesh has improved it to avoid some false positives, but from from
> >> the commit message it seems that although unlikely it might still be
> >> possible. Could you post the output to see if this is the case?
> >
> > I think Michael said he saw that failure in 2.33 and not on 2.34,
> > which is how it should be with my fix.
>
> But the test was added only on 2.34 (assuming he is testing with the release
> package). Micheal, are you using the source package or some repository revision?
No, the safe linking test was added in 2.32.
Siddhesh
next prev parent reply other threads:[~2021-08-04 12:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 16:15 Michael Brunnbauer
2021-08-03 16:32 ` Siddhesh Poyarekar
2021-08-04 11:56 ` Adhemerval Zanella
2021-08-04 12:00 ` Siddhesh Poyarekar
2021-08-04 12:03 ` Adhemerval Zanella
2021-08-04 12:08 ` Siddhesh Poyarekar [this message]
2021-08-04 12:10 ` Adhemerval Zanella
2021-08-04 12:12 ` Siddhesh Poyarekar
2021-08-04 12:29 ` Michael Brunnbauer
2021-08-04 20:12 ` Adhemerval Zanella
2021-08-05 11:13 ` Michael Brunnbauer
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=CAAmeS-ZQfa0ephHSCxgTBUd69pcE40PtXxrKDqnCBn0FWnKqXQ@mail.gmail.com \
--to=siddhesh@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=brunni@netestate.de \
--cc=libc-help@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).