public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: builder@sourceware.org
To: gdb-testers@sourceware.org
Subject: ☝ Buildbot (Sourceware): binutils-gdb - worker not available (master)
Date: Tue, 02 May 2023 16:51:18 +0000 [thread overview]
Message-ID: <20230502165118.7CC6D3858D28@sourceware.org> (raw)
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/3581
Build state: worker not available
Revision: (unknown)
Worker: bbo1-1
Build Reason: (unknown)
Blamelist: Aditya Kamath <Aditya.Kamath1@ibm.com>, Andrew Burgess <aburgess@redhat.com>, GDB Administrator <gdbadmin@sourceware.org>, Nick Clifton <nickc@redhat.com>, Simon Marchi <simon.marchi@efficios.com>, Tom Tromey <tom@tromey.com>, Tom Tromey <tromey@adacore.com>, Tom de Vries <tdevries@suse.de>
Steps:
- 0: worker_preparation ( exception )
A new failure 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/3578
Build state: failed update (failure)
Revision: (unknown)
Worker: bbo1-1
Build Reason: (unknown)
Blamelist: Tom de Vries <tdevries@suse.de>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/98/builds/3578/steps/1/logs/stdio
next reply other threads:[~2023-05-02 16:51 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 16:51 builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-02 1:30 builder
2024-03-09 2:26 builder
2024-02-27 21:51 builder
2024-02-21 9:24 builder
2024-02-08 23:37 builder
2024-01-21 16:51 builder
2024-01-19 17:49 builder
2024-01-19 17:14 builder
2024-01-10 15:33 builder
2024-01-09 14:42 builder
2024-01-09 13:18 builder
2023-12-21 8:37 builder
2023-12-21 7:48 builder
2023-12-20 11:55 builder
2023-12-13 9:21 builder
2023-12-08 7:15 builder
2023-11-23 2:37 builder
2023-11-23 2:28 builder
2023-11-23 2:26 builder
2023-11-23 2:25 builder
2023-11-23 2:24 builder
2023-11-21 14:37 builder
2023-11-14 19:29 builder
2023-11-12 14:02 builder
2023-10-28 21:19 builder
2023-10-20 4:18 builder
2023-10-10 15:55 builder
2023-08-12 6:59 builder
2023-08-12 6:42 builder
2023-08-01 20:14 builder
2023-07-17 12:58 builder
2023-07-17 8:51 builder
2023-06-27 20:16 builder
2023-05-30 23:27 builder
2023-04-14 1:13 builder
2023-03-30 18:46 builder
2023-03-27 15:45 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=20230502165118.7CC6D3858D28@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).