From: Sergio Durigan Junior <sergiodj@redhat.com>
To: gdb-buildbot@sergiodj.net
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
Subject: Re: Oh dear. I regret to inform you that commit b4be9bfdabb57f40656e72a50a8466af4f7bd37d might be unfortunate
Date: Thu, 12 Apr 2018 20:45:00 -0000 [thread overview]
Message-ID: <87r2nknogr.fsf@redhat.com> (raw)
In-Reply-To: <b4be9bfdabb57f40656e72a50a8466af4f7bd37d-master-breakage@gdb-build> (gdb-buildbot@sergiodj.net's message of "Thu, 12 Apr 2018 16:34:28 -0400")
On Thursday, April 12 2018, 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:
>
> Fix -D_GLIBCXX_DEBUG gdb-add-index regression
> b4be9bfdabb57f40656e72a50a8466af4f7bd37d
>
> 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.
Please ignore these breakage messages.
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
prev parent reply other threads:[~2018-04-12 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 20:34 gdb-buildbot
2018-04-12 20:34 ` Breakage on builder Fedora-i686, revision b4be9bfdabb57f40656e72a50a8466af4f7bd37d gdb-buildbot
2018-04-12 20:45 ` Sergio Durigan Junior [this message]
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=87r2nknogr.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-buildbot@sergiodj.net \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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