Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: gdb-buildbot@sergiodj.net, Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Oh dear. I regret to inform you that commit 970d89d8fdd84b31decaf3bd84e785aad057ea32 might be unfortunate
Date: Wed, 21 Nov 2018 10:16:00 -0000	[thread overview]
Message-ID: <ydd36ruivla.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <970d89d8fdd84b31decaf3bd84e785aad057ea32-master-breakage@gdb-build>	(gdb-buildbot@sergiodj.net's message of "Tue, 20 Nov 2018 11:55:43	-0500")

Hi Sergio,

> My lords, ladies, gentlemen, members of the public.
>
> It is a matter of great regret and sadness to inform you that commit:
>
> 	Avoid "Invalid parameter passed to C runtime function" warning
> 	970d89d8fdd84b31decaf3bd84e785aad057ea32
>
> 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.

I noticed that the corresponding messages for the Solaris buildbots
didn't arrive on gdb-patches for some reason, although the builds failed
just the same.  Both buildbots have the MAIL tag set and I'm pretty
certain this worked in the beginning once the bots were stable and you
set the tag.  I've already seens thi at least once before.  Is this
some problem on the bots?  I'd have thought the mails were sent by the
buildmaster.

Thanks.
        Rainer

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


  parent reply	other threads:[~2018-11-21 10:16 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 ` Rainer Orth [this message]
2018-11-21 18:25   ` Oh dear. I regret to inform you that commit 970d89d8fdd84b31decaf3bd84e785aad057ea32 might be unfortunate Sergio Durigan Junior
2018-11-22  9:52     ` Rainer Orth
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=ydd36ruivla.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