public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: builder@sourceware.org To: gdb-testers@sourceware.org Subject: ☝ Buildbot (GNU Toolchain): binutils-gdb - worker cannot substantiate (master) Date: Mon, 24 Oct 2022 00:22:38 +0000 [thread overview] Message-ID: <20221024002238.D1C4F3856DD2@sourceware.org> (raw) A build exception 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/1510 Build state: worker cannot substantiate Revision: (unknown) Worker: bb1-1 Build Reason: (unknown) Blamelist: GDB Administrator <gdbadmin@sourceware.org> Steps: - 0: worker_preparation ( exception ) Logs: - err.text: https://builder.sourceware.org/buildbot/#builders/74/builds/1510/steps/0/logs/err_text - err.html: https://builder.sourceware.org/buildbot/#builders/74/builds/1510/steps/0/logs/err_html A build exception has been detected on builder gdb-rawhide-x86_64 while building binutils-gdb. Full details are available at: https://builder.sourceware.org/buildbot/#builders/136/builds/899 Build state: worker cannot substantiate Revision: (unknown) Worker: bb3 Build Reason: (unknown) Blamelist: GDB Administrator <gdbadmin@sourceware.org> Steps: - 0: worker_preparation ( exception ) Logs: - err.text: https://builder.sourceware.org/buildbot/#builders/136/builds/899/steps/0/logs/err_text - err.html: https://builder.sourceware.org/buildbot/#builders/136/builds/899/steps/0/logs/err_html
next reply other threads:[~2022-10-24 0:22 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-24 0:22 builder [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-12-25 15:21 builder 2022-11-20 14:20 builder 2022-06-18 18:32 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=20221024002238.D1C4F3856DD2@sourceware.org \ --to=builder@sourceware.org \ --cc=gdb-testers@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).