From: builder@sourceware.org
To: "Nick Clifton" <nickc@redhat.com>, "Tom de Vries" <tdevries@suse.de>
Cc: binutils@sourceware.org
Subject: ☠ Buildbot (Sourceware): binutils-snapshots - failed update (failure) (master)
Date: Tue, 04 Feb 2025 12:09:51 +0000 [thread overview]
Message-ID: <20250204120951.9B6823858C60@sourceware.org> (raw)
A new failure has been detected on builder binutils-snapshots while building binutils-gdb.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/305/builds/795
Build state: failed update (failure)
Revision: (unknown)
Worker: snapshots
Build Reason: (unknown)
Blamelist: Nick Clifton <nickc@redhat.com>, Tom de Vries <tdevries@suse.de>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/305/builds/795/steps/1/logs/stdio
next reply other threads:[~2025-02-04 12:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 12:09 builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-05 16:46 builder
2025-01-17 9:07 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=20250204120951.9B6823858C60@sourceware.org \
--to=builder@sourceware.org \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
--cc=tdevries@suse.de \
/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).