Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Sergio Durigan Junior <sergiodj@redhat.com>
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: Thu, 22 Nov 2018 09:52:00 -0000	[thread overview]
Message-ID: <yddlg5lh21i.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <87sgzu70f2.fsf@redhat.com> (Sergio Durigan Junior's message of	"Wed, 21 Nov 2018 13:25:37 -0500")

Hi Sergio,

> 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.

> Thanks for the report.

Thank you so much for all your work on the buildbot.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University


  reply	other threads:[~2018-11-22  9:52 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 [this message]
2018-11-26 16:51       ` Sergio Durigan Junior
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=yddlg5lh21i.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=gdb-buildbot@sergiodj.net \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@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