From: "Andre Vieira (lists)" <andre.simoesdiasvieira@arm.com>
To: gdb-patches@sourceware.org
Subject: Re: Oh dear. I regret to inform you that commit 73cd51e51b294af9591ecc2e8a28a9bec4f466b3 might be unfortunate
Date: Thu, 16 May 2019 16:16:00 -0000 [thread overview]
Message-ID: <f7aa5cfa-05f1-9952-e24a-980d6d8f38c5@arm.com> (raw)
In-Reply-To: <73cd51e51b294af9591ecc2e8a28a9bec4f466b3-master-breakage@gdb-build>
Worry not oh faithful GDB BuildBot, your next build will surely succeed!
This failure is due to the poor structuring on my part of the patch
series that introduces a "framework" change that defines function
parameters to be used in subsequent patches in the series.
Cheers,
Andre
On 16/05/2019 16:59, gdb-buildbot@sergiodj.net wrote:
> My lords, ladies, gentlemen, members of the public.
>
> It is a matter of great regret and sadness to inform you that commit:
>
> [PATCH 37/57][Arm][OBJDUMP] Add framework for MVE instructions
> 73cd51e51b294af9591ecc2e8a28a9bec4f466b3
>
> might have made GDB unwell. Since I am just your Butler BuildBot,
> I kindly ask that a human superior officer double-check this.
>
> Please note that if you are reading this message on gdb-patches, there might
> be other builders broken.
>
> You can find more details about the unfortunate breakage in the next messages.
>
> Cheers,
>
> Your GDB BuildBot.
>
next prev parent reply other threads:[~2019-05-16 16:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 15:59 gdb-buildbot
2019-05-16 16:16 ` Andre Vieira (lists) [this message]
2019-05-16 16:31 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, revision 73cd51e51b294af9591ecc2e8a28a9bec4f466b3 gdb-buildbot
2019-05-16 16:33 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2019-05-16 16:33 ` Breakage on builder Fedora-x86_64-cc-with-index, " gdb-buildbot
2019-05-16 16:35 ` Breakage on builder Fedora-x86_64-w64-mingw32, " gdb-buildbot
2019-05-16 16:35 ` Breakage on builder Fedora-x86_64-m64, " gdb-buildbot
2019-05-16 16:35 ` Breakage on builder Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
2019-05-16 16:37 ` Breakage on builder Fedora-i686, " gdb-buildbot
2019-05-16 16:37 ` Breakage on builder Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2019-05-16 16:40 ` Breakage on builder Fedora-x86_64-m32, " gdb-buildbot
2019-05-16 17:39 ` Breakage on builder Debian-s390x-native-gdbserver-m64, " gdb-buildbot
2019-05-16 17:47 ` Breakage on builder Debian-s390x-m64, " gdb-buildbot
2019-05-16 17:54 ` Breakage on builder Debian-s390x-native-extended-gdbserver-m64, " gdb-buildbot
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=f7aa5cfa-05f1-9952-e24a-980d6d8f38c5@arm.com \
--to=andre.simoesdiasvieira@arm.com \
--cc=gdb-patches@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