From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Breakage on builder Ubuntu-Aarch64-native-extended-gdbserver-m64, revision 4ada3dfd5c07f0f1045a721a28fc905918ffbdfd
Date: Wed, 02 Jan 2019 18:06:00 -0000 [thread overview]
Message-ID: <87wonnvsrx.fsf@redhat.com> (raw)
In-Reply-To: <20190102063417.GA28188@adacore.com> (Joel Brobecker's message of "Wed, 2 Jan 2019 10:34:17 +0400")
On Wednesday, January 02 2019, Joel Brobecker wrote:
>> Unfortunately it seems that there is a breakage on GDB.
>>
>> Commit title: 'Fix year range in unittests/.../char/empty.cc copyright header'
>> Revision: 4ada3dfd5c07f0f1045a721a28fc905918ffbdfd
>
> Looks unrelated to my change (error in gnulib)...
Indeed, something when wrong with the buildslave when compiling this
commit. The breakage disappeared on the next commit:
https://gdb-build.sergiodj.net/builders/Ubuntu-Aarch64-native-extended-gdbserver-m64/builds/366
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/
prev parent reply other threads:[~2019-01-02 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 6:29 Oh dear. I regret to inform you that commit 4ada3dfd5c07f0f1045a721a28fc905918ffbdfd might be unfortunate gdb-buildbot
2019-01-02 6:29 ` Breakage on builder Ubuntu-Aarch64-native-extended-gdbserver-m64, revision 4ada3dfd5c07f0f1045a721a28fc905918ffbdfd gdb-buildbot
2019-01-02 6:34 ` Joel Brobecker
2019-01-02 18:06 ` Sergio Durigan Junior [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=87wonnvsrx.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