From: Mark Wielaard <mark@klomp.org>
To: binutils@sourceware.org
Subject: Re: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed update (failure) (master)
Date: Thu, 19 May 2022 13:11:54 +0200 [thread overview]
Message-ID: <855ba7f2237829ad484b4ddbaf9345a2992ddd6c.camel@klomp.org> (raw)
In-Reply-To: <20220519105816.B669A385040D@sourceware.org>
Hi,
On Thu, 2022-05-19 at 10:58 +0000, builder--- via Binutils wrote:
> A new failure has been detected on builder binutils-fedora-ppc64le
> while building binutils-gdb.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/86/builds/36
>
> Build state: failed update (failure)
> Revision: (unknown)
> Worker: fedora-ppc64le
> Build Reason: (unknown)
> Blamelist: Jan Beulich <jbeulich@suse.com>
>
> Steps:
>
> - 0: worker_preparation ( success )
>
> - 1: git checkout ( failure )
> Logs:
> - stdio:
> https://builder.sourceware.org/buildbot/#builders/86/builds/36/steps/1/logs/stdio
Sorry about that. That was obviously just a network/git transport
issue. I have restarted that build and it seems fine now.
https://builder.sourceware.org/buildbot/#/builders/86
Note that the builder did find a real issue with:
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=3363d8560ff5229b724827a77b533ec8b2a23729
commit 3363d8560ff5229b724827a77b533ec8b2a23729
Author: Victor Do Nascimento <victor.donascimento@arm.com>
Date: Wed May 18 16:25:12 2022 +0100
arm: Add unwind support for mixed register lists
* config/tc-arm.c (parse_reg_list): Add handling of mixed register
types.
(reg_names): Enumerate pseudoregister according to mapped physical
register number.
(s_arm_unwind_save_pseudo): Modify function signature.
(s_arm_unwind_save_core): Likewise.
(s_arm_unwind_save_mixed): New function.
(s_arm_unwind_save): Generate register list mask to pass to nested
functions.
* testsuite/gas/arm/unwind-pacbti-m.s: Expand test for mixed
register type lists.
* testsuite/gas/arm/unwind-pacbti-m.d: Likewise.
* testsuite/gas/arm/unwind-pacbti-m-readelf.d: Likewise.
https://builder.sourceware.org/buildbot/#/changes/1165
https://builder.sourceware.org/buildbot/#/builders/80/builds/68
../../binutils-gdb/gas/config/tc-arm.c: In function ‘s_arm_unwind_save_mixed’:
../../binutils-gdb/gas/config/tc-arm.c:4730:17: error: comparison of integer expressions of different signedness: ‘unsigned int’ and ‘long int’ [-Werror=sign-compare]
for (; lim_hi <= roof; lim_hi++)
^~
cc1: all warnings being treated as errors
make[3]: *** [Makefile:1423: config/tc-arm.o] Error 1
But didn't report it through email because armhf was already failing
the testsuite, so the buildbot didn't believe this was a new failure.
Cheers,
Mark
next prev parent reply other threads:[~2022-05-19 11:11 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 10:58 builder
2022-05-19 11:11 ` Mark Wielaard [this message]
2022-06-02 9:24 builder
2022-06-24 0:21 builder
2022-06-27 0:18 builder
2022-06-28 1:23 builder
2022-06-29 11:35 builder
2022-07-04 10:43 builder
2022-07-16 0:23 builder
2022-07-19 14:38 builder
2022-07-21 19:41 builder
2022-07-22 0:52 ` Luis Machado
2022-07-22 9:58 ` Mark Wielaard
2022-08-01 1:41 builder
2022-08-05 11:37 builder
2022-08-11 5:38 builder
2022-08-13 9:02 builder
2022-08-15 15:19 builder
2022-08-16 0:19 builder
2022-08-16 7:47 builder
2022-08-20 0:19 builder
2022-08-22 2:51 builder
2022-08-23 5:29 builder
2022-08-24 6:41 builder
2022-08-25 9:17 builder
2022-08-27 5:16 builder
2022-08-30 13:04 builder
2022-09-02 6:31 builder
2022-09-02 17:15 builder
2022-09-05 0:19 builder
2022-09-06 0:21 builder
2022-09-06 15:19 builder
2022-09-08 9:15 builder
2022-09-13 13:51 builder
2022-09-14 1:55 builder
2022-09-20 11:08 builder
2022-09-22 7:24 builder
2022-09-22 17:20 builder
2022-09-22 17:43 builder
2022-09-24 0:20 builder
2022-09-26 0:38 builder
2022-09-26 5:43 builder
2022-09-26 6:04 builder
2022-09-30 1:34 builder
2022-10-03 11:59 builder
2022-10-04 13:34 builder
2022-10-05 0:19 builder
2022-10-05 4:52 builder
2022-10-06 0:25 builder
2022-10-06 4:31 builder
2022-12-17 0:34 builder
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=855ba7f2237829ad484b4ddbaf9345a2992ddd6c.camel@klomp.org \
--to=mark@klomp.org \
--cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).