From: Mark Wielaard <mark@klomp.org>
To: binutils@sourceware.org
Cc: nickc@redhat.com, Natarajan@wildebeest.org,
Kavitha <Kavitha.Natarajan@amd.com>,
Pedro Alves <pedro@palves.net>
Subject: Re: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed test (failure) (master)
Date: Wed, 25 May 2022 21:11:10 +0200 [thread overview]
Message-ID: <Yo5/TqAxk2T15rxB@wildebeest.org> (raw)
In-Reply-To: <20220525152705.70F3B382F0B6@sourceware.org>
Hi,
On Wed, May 25, 2022 at 03:27:05PM +0000, builder--- via Binutils wrote:
> A new failure has been detected on builder binutils-fedora-x86_64 while building binutils-gdb.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/77/builds/101
>
> Build state: failed test (failure)
> Revision: 3ac9da49378ccb061e3e33e4342c35949bf368a9
> Worker: fedora-x86_64
> Build Reason: (unknown)
> Blamelist: Natarajan, Kavitha <Kavitha.Natarajan@amd.com>, Pedro Alves <pedro@palves.net>
The buildbot blame doesn't know it was actually Nick who did the
commit/push. Nick, it looks like you forgot to add
binutils/testsuite/binutils-all/dw5-op.S and
binutils/testsuite/binutils-all/dw5-op.W
Causing the new testcase to FAIL.
Cheers,
Mark
next prev parent reply other threads:[~2022-05-25 19:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 15:27 builder
2022-05-25 19:11 ` Mark Wielaard [this message]
2022-07-03 16:54 builder
2022-07-03 17:30 ` Mark Wielaard
2022-07-19 1:32 builder
2022-07-25 0:24 builder
2022-09-07 0:32 builder
2022-09-19 0:37 builder
2022-09-22 7:49 builder
2022-09-26 15:57 builder
2022-09-27 3:09 builder
2022-09-28 0:20 builder
2022-09-28 1:23 builder
2022-10-11 12:35 builder
2022-10-19 7:35 builder
[not found] <20221019073533.3F8543858D3C@sourceware.org>
2022-10-19 7:55 ` Tom de Vries
2022-10-19 9:02 ` Alan Modra
2022-11-02 2:50 builder
2022-11-02 3:06 ` Jiang, Haochen
2022-11-16 1:09 builder
2022-11-16 3:50 ` Indu Bhagat
2022-12-23 21:30 builder
2022-12-23 22:10 ` Indu Bhagat
2022-12-24 1:46 ` Mike Frysinger
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=Yo5/TqAxk2T15rxB@wildebeest.org \
--to=mark@klomp.org \
--cc=Kavitha.Natarajan@amd.com \
--cc=Natarajan@wildebeest.org \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
--cc=pedro@palves.net \
/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).