From: Joseph Myers <joseph@codesourcery.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: Martin Sebor <msebor@gmail.com>, "H.J. Lu" <hjl.tools@gmail.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: tests failing on x86_64-linux (due to test-container?)
Date: Mon, 17 Jan 2022 19:09:10 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2201171908410.489193@digraph.polyomino.org.uk> (raw)
In-Reply-To: <160ec0c7-e3e5-c060-41dc-2a604d2dacb2@linaro.org>
On Mon, 17 Jan 2022, Adhemerval Zanella via Libc-alpha wrote:
> > XPASS: elf/tst-protected1a
> > XPASS: elf/tst-protected1b
>
> These are marked XFAIL because a gcc and binutils issue [1] [2].
> I think with current minimum supported versions we can remove
> the xfail.
I think this only works on a few architectures.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-01-17 19:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 18:17 tests failing on x86_64-linux Martin Sebor
2020-12-09 18:28 ` H.J. Lu
2020-12-09 21:17 ` Martin Sebor
2020-12-09 21:44 ` H.J. Lu
2020-12-09 22:31 ` H.J. Lu
2020-12-10 2:50 ` H.J. Lu
2020-12-15 0:55 ` Martin Sebor
2021-04-28 20:07 ` tests failing on x86_64-linux (due to test-container?) Martin Sebor
2021-04-28 20:37 ` DJ Delorie
2021-04-28 21:50 ` Martin Sebor
2021-04-28 23:08 ` DJ Delorie
2021-04-28 23:42 ` Martin Sebor
2021-04-28 23:54 ` DJ Delorie
2021-05-13 21:29 ` Martin Sebor
2022-01-12 22:04 ` Martin Sebor
2022-01-12 22:13 ` H.J. Lu
2022-01-12 23:24 ` Martin Sebor
2022-01-14 23:51 ` Martin Sebor
2022-01-17 18:04 ` Adhemerval Zanella
2022-01-17 19:09 ` Joseph Myers [this message]
2022-01-20 22:23 ` Martin Sebor
2020-12-16 10:21 ` tests failing on x86_64-linux Florian Weimer
2020-12-09 19:03 ` Florian Weimer
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=alpine.DEB.2.22.394.2201171908410.489193@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=msebor@gmail.com \
/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).