This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Oh dear. I regret to inform you that commit 23c4651c060c123493de004ef61d8ed052d46113 might be unfortunate
- From: Sergio Durigan Junior <sergiodj at redhat dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 10 Sep 2018 11:29:49 -0400
- Subject: Re: Oh dear. I regret to inform you that commit 23c4651c060c123493de004ef61d8ed052d46113 might be unfortunate
- References: <23c4651c060c123493de004ef61d8ed052d46113-master-breakage@gdb-build> <83in3dpzed.fsf@gnu.org>
On Monday, September 10 2018, Eli Zaretskii wrote:
>> From: gdb-buildbot@sergiodj.net
>> Date: Mon, 10 Sep 2018 03:19:34 -0400
>>
>> My lords, ladies, gentlemen, members of the public.
>>
>> It is a matter of great regret and sadness to inform you that commit:
>>
>> Fix "make install-strip" failure to install gdb-add-index.sh
>> 23c4651c060c123493de004ef61d8ed052d46113
>>
>> might have made GDB unwell. Since I am just your Butler BuildBot,
>> I kindly ask that a human superior officer double-check this.
>
> It is clear from the build log that the breakage has nothing to do
> with the change I committed. In particular, the offending parts of
> gnulib's glob.c were not modified by my commit, but by Sergio's commit
> 7a6dbc2 of 2 weeks ago. Why is this being flagged only now?
Hi Eli,
There must have been some problem with the locking mechanism which
prevents the BuildBot from flagging the same breakage many times. Sorry
about that. Also, a few of the buildslaves are lagging behind and
having a hard time keeping up with the builds. Anyway, I'm back to work
today and will submit a patch to fix this failure soon.
Thanks for the patience,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/