From: gdb-buildbot@sergiodj.net
To: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Oh dear. I regret to inform you that commit 2edf834e298b15c882678db22e86745f701807fa might be unfortunate
Date: Thu, 19 Oct 2017 15:46:00 -0000 [thread overview]
Message-ID: <2edf834e298b15c882678db22e86745f701807fa-master-breakage@gdb-build> (raw)
My lords, ladies, gentlemen, members of the public.
It is a matter of great regret and sadness to inform you that commit:
xml_fetch_content_from_file: Read in whole file in one go
2edf834e298b15c882678db22e86745f701807fa
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 reply other threads:[~2017-10-19 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 15:46 gdb-buildbot [this message]
2017-10-19 15:46 ` Breakage on builder Ubuntu-AArch64-native-gdbserver-m64, revision 2edf834e298b15c882678db22e86745f701807fa gdb-buildbot
2017-10-19 15:58 ` Breakage on builder Ubuntu-AArch64-m64, " gdb-buildbot
2017-10-19 16:15 ` Breakage on builder Ubuntu-AArch32-m32, " gdb-buildbot
2017-10-19 16:31 ` Breakage on builder Ubuntu-AArch32-native-extended-gdbserver-m32, " gdb-buildbot
2017-10-19 16:47 ` Breakage on builder Ubuntu-AArch32-native-gdbserver-m32, " gdb-buildbot
2017-10-19 17:23 ` Oh dear. I regret to inform you that commit 2edf834e298b15c882678db22e86745f701807fa might be unfortunate Pedro Alves
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=2edf834e298b15c882678db22e86745f701807fa-master-breakage@gdb-build \
--to=gdb-buildbot@sergiodj.net \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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