Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Oh dear. I regret to inform you that commit 'remove param "dispp" from ada-lang.c::ada_lookup_struct_elt_type' might be unfortunate
Date: Sat, 26 Aug 2017 19:54:00 -0000	[thread overview]
Message-ID: <87mv6m9kbt.fsf@redhat.com> (raw)
In-Reply-To: <20170826123906.wg5s7qsm65lklk5s@adacore.com> (Joel Brobecker's	message of "Sat, 26 Aug 2017 08:39:06 -0400")

On Saturday, August 26 2017, Joel Brobecker wrote:

> Hello,
>
> On Fri, Aug 25, 2017 at 08:48:58PM -0400, gdb-buildbot@sergiodj.net wrote:
>> My lords, ladies, gentlemen, members of the public.
>> 
>> It is a matter of great regret and sadness to inform you that commit:
>> 
>> 	remove param "dispp" from ada-lang.c::ada_lookup_struct_elt_type
>> 	988f6b3dc615173d6d78a76ac26c109b4582da74
>> 
>> might have made GDB unwell.  Since I am just your Butler BuildBot,
>> I kindly ask that a human superior officer double-check this.
>
> My change only touches a static function in ada-lang.c, while
> the error is reported inside sparc64-tdep.  Maybe an earlier commit?

Yeah, sorry about these messages.  BuildBot is currently not smart
enough to figure out that the failure was not introduced by the last
commit.  One solution, proposed by Pedro, is to send the breakage e-mail
to the authors of all commits that haven't been tested until the last
one, but that's also not easy to do...  I'll investigate and see if
there's any other way.

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/


  parent reply	other threads:[~2017-08-26 19:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1dlPHW-0007LM-Eg@kwanyin.sergiodj.net>
2017-08-26 12:39 ` Joel Brobecker
2017-08-26 13:18   ` Simon Marchi
2017-08-26 19:54   ` Sergio Durigan Junior [this message]
2017-08-26 21:04     ` H.J. Lu

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=87mv6m9kbt.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=brobecker@adacore.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