Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Oh dear. I regret to inform you that commit 1ef8573cc77c91feeef3edab74d383d20809eb33 might be unfortunate
Date: Thu, 10 Jan 2019 17:12:00 -0000	[thread overview]
Message-ID: <1ef8573cc77c91feeef3edab74d383d20809eb33-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:

	gdb: Improve scoped_switch_fork_info class
	1ef8573cc77c91feeef3edab74d383d20809eb33

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.


             reply	other threads:[~2019-01-10 17:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 17:12 gdb-buildbot [this message]
2019-01-10 17:12 ` Breakage on builder RHEL-s390x-m64, revision 1ef8573cc77c91feeef3edab74d383d20809eb33 gdb-buildbot
2019-01-11 16:58 ` Breakage on builder Debian-s390x-native-extended-gdbserver-m64, " gdb-buildbot
2019-01-11 17:00 ` Breakage on builder Debian-s390x-native-gdbserver-m64, " gdb-buildbot
2019-01-11 17:02 ` Breakage on builder Debian-s390x-m64, " gdb-buildbot
2019-01-12  1:40 ` Breakage on builder Fedora-i686, " gdb-buildbot
2019-01-12  1:45 ` Breakage on builder Fedora-x86_64-cc-with-index, " gdb-buildbot
2019-01-12  1:47 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2019-01-12  1:50 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2019-01-12  1:54 ` Breakage on builder Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
2019-01-12  1:56 ` Breakage on builder Fedora-x86_64-m64, " gdb-buildbot
2019-01-12  2:02 ` Breakage on builder Fedora-x86_64-m32, " gdb-buildbot
2019-01-12  2:17 ` Breakage on builder Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2019-01-14 16:47 ` Breakage on builder Ubuntu-Aarch64-native-extended-gdbserver-m64, " gdb-buildbot
2019-01-14 16:54 ` Breakage on builder Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot
2019-01-14 17:02 ` Breakage on builder Ubuntu-Aarch64-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=1ef8573cc77c91feeef3edab74d383d20809eb33-master-breakage@gdb-build \
    --to=gdb-buildbot@sergiodj.net \
    --cc=andrew.burgess@embecosm.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