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 - preparing worker (master) Date: Sun, 16 Oct 2022 19:38:44 +0000 [thread overview] Message-ID: <20221016193844.0D75D3858D3C@sourceware.org> (raw) A retry build has been detected on builder gdb-debian-testing-x86_64 while building binutils-gdb. Full details are available at: https://builder.sourceware.org/buildbot/#builders/148/builds/787 Build state: preparing worker Revision: (unknown) Worker: bb2-1 Build Reason: (unknown) Blamelist: Tom Tromey <tom@tromey.com> Steps: - 0: worker_preparation ( retry ) A retry build has been detected on builder gdb-debian-testing-x86_64 while building binutils-gdb. Full details are available at: https://builder.sourceware.org/buildbot/#builders/148/builds/788 Build state: worker not available Revision: (unknown) Worker: bb2-1 Build Reason: (unknown) Blamelist: Tom Tromey <tom@tromey.com> Steps: - 0: worker_preparation ( exception ) Logs: - err.text: https://builder.sourceware.org/buildbot/#builders/148/builds/788/steps/0/logs/err_text - err.html: https://builder.sourceware.org/buildbot/#builders/148/builds/788/steps/0/logs/err_html A retry build has been detected on builder gdb-debian-testing-x86_64 while building binutils-gdb. Full details are available at: https://builder.sourceware.org/buildbot/#builders/148/builds/789 Build state: worker not available Revision: (unknown) Worker: bb2-1 Build Reason: (unknown) Blamelist: Tom Tromey <tom@tromey.com> Steps: - 0: worker_preparation ( exception ) Logs: - err.text: https://builder.sourceware.org/buildbot/#builders/148/builds/789/steps/0/logs/err_text - err.html: https://builder.sourceware.org/buildbot/#builders/148/builds/789/steps/0/logs/err_html
reply other threads:[~2022-10-16 19:38 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221016193844.0D75D3858D3C@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).