public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/24521] [readnow] Testsuite FAILs
Date: Wed, 28 Oct 2020 20:44:04 +0000 [thread overview]
Message-ID: <bug-24521-4717-UeKgPRJR1v@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24521-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24521
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |11.1
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #11 from Tom de Vries <vries at gcc dot gnu.org> ---
With current trunk I'm getting the same amount of "unexpected failures" with
target board readnow, as with native.
There are still issues remaining, but individual bugs are open for that, and
referenced using kfail.
There's no longer a need for a catch-all PR.
Marking resolved-fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-10-28 20:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-24521-4717@http.sourceware.org/bugzilla/>
2020-04-08 15:11 ` [Bug testsuite/24521] readnow failures vries at gcc dot gnu.org
2020-04-21 6:43 ` vries at gcc dot gnu.org
2020-04-29 9:43 ` [Bug testsuite/24521] [readnow] Testsuite FAILs vries at gcc dot gnu.org
2020-10-22 7:33 ` vries at gcc dot gnu.org
2020-10-28 20:44 ` vries at gcc dot gnu.org [this message]
2020-10-29 13:45 ` simark at simark dot ca
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=bug-24521-4717-UeKgPRJR1v@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).