public inbox for gdbadmin@sourceware.org help / color / mirror / Atom feed
From: builder@sourceware.org To: "Alan Modra" <amodra@gmail.com>, "Andrew Burgess" <aburgess@redhat.com>, "GDB Administrator" <gdbadmin@sourceware.org>, "Hans-Peter Nilsson" <hp@axis.com>, "Indu Bhagat" <indu.bhagat@oracle.com>, "Nick Alcock" <nick.alcock@oracle.com>, "Nick Clifton" <nickc@redhat.com>, "Tom Tromey" <tom@tromey.com>, "Tom Tromey" <tromey@adacore.com>, "Vladimir Mezentsev" <vladimir.mezentsev@oracle.com> Subject: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed compile (failure) (master) Date: Fri, 13 Jan 2023 22:26:45 +0000 [thread overview] Message-ID: <20230113222645.E219F383FB84@sourceware.org> (raw) A new failure has been detected on builder gdb-centos-x86_64 while building binutils-gdb. Full details are available at: https://builder.sourceware.org/buildbot/#builders/71/builds/2523 Build state: failed compile (failure) Revision: fc5ab4bc44e77fbc5aee61d46e8b6f23bef8b371 Worker: centos-x86_64 Build Reason: (unknown) Blamelist: Alan Modra <amodra@gmail.com>, Andrew Burgess <aburgess@redhat.com>, GDB Administrator <gdbadmin@sourceware.org>, Hans-Peter Nilsson <hp@axis.com>, Indu Bhagat <indu.bhagat@oracle.com>, Nick Alcock <nick.alcock@oracle.com>, Nick Clifton <nickc@redhat.com>, Tom Tromey <tom@tromey.com>, Tom Tromey <tromey@adacore.com>, Vladimir Mezentsev <vladimir.mezentsev@oracle.com> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/71/builds/2523/steps/1/logs/stdio - 2: rm -rf gdb-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/71/builds/2523/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/71/builds/2523/steps/3/logs/stdio - 4: make ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/71/builds/2523/steps/4/logs/stdio - warnings (63): https://builder.sourceware.org/buildbot/#builders/71/builds/2523/steps/4/logs/warnings__63_
next reply other threads:[~2023-01-13 22:26 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-13 22:26 builder [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-01-15 23:45 builder 2022-12-05 0:18 builder 2022-10-19 0:24 builder 2022-06-09 0:26 builder 2022-06-09 0:20 builder 2022-06-09 9:32 ` Andrew Burgess 2022-06-09 10:00 ` Mark Wielaard
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=20230113222645.E219F383FB84@sourceware.org \ --to=builder@sourceware.org \ --cc=aburgess@redhat.com \ --cc=amodra@gmail.com \ --cc=gdbadmin@sourceware.org \ --cc=hp@axis.com \ --cc=indu.bhagat@oracle.com \ --cc=nick.alcock@oracle.com \ --cc=nickc@redhat.com \ --cc=tom@tromey.com \ --cc=tromey@adacore.com \ --cc=vladimir.mezentsev@oracle.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: linkBe 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).