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 not available (master)
Date: Sat, 05 Nov 2022 04:04:50 +0000 [thread overview]
Message-ID: <20221105040450.276BF385E00F@sourceware.org> (raw)
A retry build 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/1642
Build state: worker not available
Revision: (unknown)
Worker: bb2-2
Build Reason: (unknown)
Blamelist: Mike Frysinger <vapier@gentoo.org>
Steps:
- 0: worker_preparation ( exception )
Logs:
- err.text: https://builder.sourceware.org/buildbot/#builders/74/builds/1642/steps/0/logs/err_text
- err.html: https://builder.sourceware.org/buildbot/#builders/74/builds/1642/steps/0/logs/err_html
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/1643
Build state: failed update (failure)
Revision: (unknown)
Worker: bb2-2
Build Reason: (unknown)
Blamelist: Mike Frysinger <vapier@gentoo.org>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/74/builds/1643/steps/1/logs/stdio
A retry build has been detected on builder gdb-opensusetw-x86_64 while building binutils-gdb.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/97/builds/1355
Build state: worker not available
Revision: (unknown)
Worker: bb1-2
Build Reason: (unknown)
Blamelist: Mike Frysinger <vapier@gentoo.org>
Steps:
- 0: worker_preparation ( exception )
Logs:
- err.text: https://builder.sourceware.org/buildbot/#builders/97/builds/1355/steps/0/logs/err_text
- err.html: https://builder.sourceware.org/buildbot/#builders/97/builds/1355/steps/0/logs/err_html
A retry build has been detected on builder gdb-opensuseleap-x86_64 while building binutils-gdb.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/98/builds/1356
Build state: worker not available
Revision: (unknown)
Worker: bb1-1
Build Reason: (unknown)
Blamelist: Mike Frysinger <vapier@gentoo.org>
Steps:
- 0: worker_preparation ( exception )
Logs:
- err.text: https://builder.sourceware.org/buildbot/#builders/98/builds/1356/steps/0/logs/err_text
- err.html: https://builder.sourceware.org/buildbot/#builders/98/builds/1356/steps/0/logs/err_html
next reply other threads:[~2022-11-05 4:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 4:04 builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-14 1:45 builder
2023-01-14 1:35 builder
2023-01-13 22:40 builder
2022-12-23 15:39 builder
2022-12-22 3:59 builder
2022-12-15 21:37 builder
2022-10-19 4:18 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=20221105040450.276BF385E00F@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: 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).