From: gdb-buildbot@sergiodj.net
To: gdb-patches@sourceware.org
To: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Oh dear. I regret to inform you that commit 098f9ed48e1c94a2624c825ba93d72b163d41196 might be unfortunate
Date: Thu, 18 Jul 2019 01:05:00 -0000 [thread overview]
Message-ID: <098f9ed48e1c94a2624c825ba93d72b163d41196-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:
Always create an execution info window for a source window
098f9ed48e1c94a2624c825ba93d72b163d41196
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:[~2019-07-18 1:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 1:05 gdb-buildbot [this message]
2019-07-18 1:05 ` Breakage on builder Solaris11-sparcv9-m64, revision 098f9ed48e1c94a2624c825ba93d72b163d41196 gdb-buildbot
2019-07-18 13:59 ` Tom Tromey
2019-07-18 1:36 ` Breakage on builder Solaris11-amd64-m64, " gdb-buildbot
2019-07-18 2:32 ` Breakage on builder NetBSD-x86_64-m64, " gdb-buildbot
2019-07-19 12:56 ` Breakage on builder Fedora-x86_64-cc-with-index, " gdb-buildbot
2019-07-19 12:58 ` Breakage on builder Fedora-x86_64-m32, " gdb-buildbot
2019-07-19 13:03 ` Breakage on builder Fedora-x86_64-m64, " gdb-buildbot
2019-07-19 13:06 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2019-07-19 13:10 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2019-07-19 13:13 ` Breakage on builder Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
2019-07-19 14:14 ` Breakage on builder Fedora-x86_64-native-gdbserver-m32, " 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=098f9ed48e1c94a2624c825ba93d72b163d41196-master-breakage@gdb-build \
--to=gdb-buildbot@sergiodj.net \
--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