From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gdb-buildbot@sergiodj.net, gdb-patches@sourceware.org
Subject: Re: Oh dear. I regret to inform you that commit 970d89d8fdd84b31decaf3bd84e785aad057ea32 might be unfortunate
Date: Mon, 26 Nov 2018 16:51:00 -0000 [thread overview]
Message-ID: <87h8g33hq5.fsf@redhat.com> (raw)
In-Reply-To: <yddlg5lh21i.fsf@CeBiTec.Uni-Bielefeld.DE> (Rainer Orth's message of "Thu, 22 Nov 2018 10:52:41 +0100")
On Thursday, November 22 2018, Rainer Orth wrote:
> Hi Sergio,
Hey Rainer,
>> Yeah, coincidentally (or not) I noticed the exact same thing, and I'm
>> working on fixing this issue. It doesn't affect just the Solaris
>> builders; it also affects the Fedora mingw32 builder (for example).
>> I've manually fixed it for now (i.e., if there is another build
>> breakage, you will see notifications for Solaris as well), and I'm
>> working to fix the underlying issue.
>
> excellent, thanks.
Just a quick heads-up: the fix worked, and now whenever a breakage is
fixed, the Solaris builders will be "clean" to report a possible future
breakage automatically.
Thanks,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2018-11-26 16:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 16:55 gdb-buildbot
2018-11-20 16:55 ` Breakage on builder Debian-s390x-native-extended-gdbserver-m64, revision 970d89d8fdd84b31decaf3bd84e785aad057ea32 gdb-buildbot
2018-11-20 16:56 ` Breakage on builder RHEL-s390x-m64, " gdb-buildbot
2018-11-20 16:57 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2018-11-20 16:57 ` Breakage on builder Fedora-s390x-m64, " gdb-buildbot
2018-11-20 16:57 ` Breakage on builder Debian-s390x-native-gdbserver-m64, " gdb-buildbot
2018-11-20 16:57 ` Breakage on builder Fedora-x86_64-cc-with-index, " gdb-buildbot
2018-11-20 16:58 ` Breakage on builder Fedora-i686, " gdb-buildbot
2018-11-20 16:58 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2018-11-20 16:59 ` Breakage on builder Debian-s390x-m64, " gdb-buildbot
2018-11-20 17:00 ` Breakage on builder Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
2018-11-20 17:01 ` Breakage on builder Fedora-x86_64-m64, " gdb-buildbot
2018-11-20 17:01 ` Breakage on builder Ubuntu-Aarch64-native-extended-gdbserver-m64, " gdb-buildbot
2018-11-20 17:03 ` Breakage on builder Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2018-11-20 17:04 ` Breakage on builder NetBSD-x86_64-m64, " gdb-buildbot
2018-11-20 17:09 ` Kamil Rytarowski
2018-11-20 17:04 ` Breakage on builder Fedora-x86_64-m32, " gdb-buildbot
2018-11-20 17:06 ` Breakage on builder Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot
2018-11-20 17:13 ` Breakage on builder Ubuntu-Aarch64-m64, " gdb-buildbot
2018-11-21 10:16 ` Oh dear. I regret to inform you that commit 970d89d8fdd84b31decaf3bd84e785aad057ea32 might be unfortunate Rainer Orth
2018-11-21 18:25 ` Sergio Durigan Junior
2018-11-22 9:52 ` Rainer Orth
2018-11-26 16:51 ` Sergio Durigan Junior [this message]
2018-11-28 10:29 ` Rainer Orth
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=87h8g33hq5.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-buildbot@sergiodj.net \
--cc=gdb-patches@sourceware.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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