From: gdb-buildbot@sergiodj.net
To: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Oh dear. I regret to inform you that commit cd4fb1b2ffc88911e4109444ff729e31920d01ec might be unfortunate
Date: Tue, 27 Mar 2018 14:24:00 -0000 [thread overview]
Message-ID: <cd4fb1b2ffc88911e4109444ff729e31920d01ec-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:
Move DWARF index-related things to a separate file
cd4fb1b2ffc88911e4109444ff729e31920d01ec
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:[~2018-03-27 14:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 14:24 gdb-buildbot [this message]
2018-03-27 14:24 ` Breakage on builder NetBSD-x86_64-m64, revision cd4fb1b2ffc88911e4109444ff729e31920d01ec gdb-buildbot
2018-03-27 14:27 ` Breakage on builder Fedora-s390x-m64, " gdb-buildbot
2018-03-27 17:56 ` Breakage on builder Fedora-x86_64-m64, " gdb-buildbot
2018-03-27 17:57 ` Breakage on builder Fedora-i686, " gdb-buildbot
2018-03-27 18:00 ` Breakage on builder Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2018-03-27 18:03 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2018-03-27 18:03 ` Breakage on builder Fedora-x86_64-m32, " gdb-buildbot
2018-03-27 18:04 ` Breakage on builder Fedora-x86_64-cc-with-index, " gdb-buildbot
2018-03-27 18:06 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2018-03-27 18:08 ` Breakage on builder Fedora-x86_64-native-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=cd4fb1b2ffc88911e4109444ff729e31920d01ec-master-breakage@gdb-build \
--to=gdb-buildbot@sergiodj.net \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.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