From: "H.J. Lu" <hjl.tools@gmail.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>, GDB <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 21:04:00 -0000 [thread overview]
Message-ID: <CAMe9rOo=M0x+Du7_Kf+cORtnobNYgxOBDoGS8rJMkomfgg-Tiw@mail.gmail.com> (raw)
In-Reply-To: <87mv6m9kbt.fsf@redhat.com>
On Sat, Aug 26, 2017 at 12:53 PM, Sergio Durigan Junior
<sergiodj@redhat.com> wrote:
> 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.
>
You can keep track of errors for the current commit and do
not send an email if the next commit doesn't change errors.
--
H.J.
prev parent reply other threads:[~2017-08-26 21:04 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
2017-08-26 21:04 ` H.J. Lu [this message]
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='CAMe9rOo=M0x+Du7_Kf+cORtnobNYgxOBDoGS8rJMkomfgg-Tiw@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=brobecker@adacore.com \
--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