public inbox for gdbadmin@sourceware.org
help / color / mirror / Atom feed
From: builder@sourceware.org
To: "Aaron Merey" <amerey@redhat.com>,
"Bruno Larsen" <blarsen@redhat.com>, "Carl Love" <cel@us.ibm.com>,
"GDB Administrator" <gdbadmin@sourceware.org>,
"Tom Tromey" <tromey@adacore.com>
Subject: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed update (failure) (master)
Date: Sat, 16 Jul 2022 00:23:34 +0000 [thread overview]
Message-ID: <20220716002334.DF137385828E@sourceware.org> (raw)
A new failure has been detected on builder binutils-debian-amd64 while building binutils-gdb.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/68/builds/365
Build state: failed update (failure)
Revision: (unknown)
Worker: bb3
Build Reason: (unknown)
Blamelist: Aaron Merey <amerey@redhat.com>, Bruno Larsen <blarsen@redhat.com>, Carl Love <cel@us.ibm.com>, GDB Administrator <gdbadmin@sourceware.org>, Tom Tromey <tromey@adacore.com>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/365/steps/1/logs/stdio
A new failure has been detected on builder binutils-debian-testing-x86_64 while building binutils-gdb.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/149/builds/74
Build state: failed update (failure)
Revision: (unknown)
Worker: bb2
Build Reason: (unknown)
Blamelist: Aaron Merey <amerey@redhat.com>, Bruno Larsen <blarsen@redhat.com>, Carl Love <cel@us.ibm.com>, GDB Administrator <gdbadmin@sourceware.org>, Tom Tromey <tromey@adacore.com>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/149/builds/74/steps/1/logs/stdio
next reply other threads:[~2022-07-16 0:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 0:23 builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-17 0:34 builder
2022-12-17 0:30 builder
2022-10-16 17:35 builder
2022-10-16 17:24 builder
2022-10-06 0:25 builder
2022-10-05 0:19 builder
2022-09-26 0:38 builder
2022-09-24 0:20 builder
2022-09-06 0:21 builder
2022-09-05 0:19 builder
2022-08-30 0:30 builder
2022-08-28 0:28 builder
2022-08-09 0:22 builder
2022-08-02 0:25 builder
2022-07-31 0:27 builder
2022-07-28 0:20 builder
2022-07-19 0:20 builder
2022-07-13 0:23 builder
2022-07-08 8:04 builder
2022-06-30 0:24 builder
2022-06-27 0:18 builder
2022-06-25 0:25 builder
2022-06-24 0:21 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=20220716002334.DF137385828E@sourceware.org \
--to=builder@sourceware.org \
--cc=amerey@redhat.com \
--cc=blarsen@redhat.com \
--cc=cel@us.ibm.com \
--cc=gdbadmin@sourceware.org \
--cc=tromey@adacore.com \
/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).