public inbox for gdbadmin@sourceware.org help / color / mirror / Atom feed
From: builder@sourceware.org To: "GDB Administrator" <gdbadmin@sourceware.org> Subject: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed compile (failure) (master) Date: Thu, 09 Jun 2022 00:26:48 +0000 [thread overview] Message-ID: <20220609002648.72FE0386CE61@sourceware.org> (raw) A new failure has been detected on builder gdb-fedora-x86_64 while building binutils-gdb. Full details are available at: https://builder.sourceware.org/buildbot/#builders/74/builds/435 Build state: failed compile (failure) Revision: d21691eaa7e851a7600ce1f616c5289b7c69055b Worker: bb3 Build Reason: (unknown) Blamelist: GDB Administrator <gdbadmin@sourceware.org> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/74/builds/435/steps/1/logs/stdio - 2: rm -rf gdb-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/74/builds/435/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/74/builds/435/steps/3/logs/stdio - 4: make ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/74/builds/435/steps/4/logs/stdio - warnings (4): https://builder.sourceware.org/buildbot/#builders/74/builds/435/steps/4/logs/warnings__4_
next reply other threads:[~2022-06-09 0:26 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-09 0:26 builder [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-01-15 23:45 builder 2023-01-13 22:26 builder 2022-12-05 0:18 builder 2022-10-19 0:24 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=20220609002648.72FE0386CE61@sourceware.org \ --to=builder@sourceware.org \ --cc=gdbadmin@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: 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).