From: builder@sourceware.org
To: binutils@sourceware.org
Subject: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed compile (failure) (master)
Date: Mon, 31 Oct 2022 13:36:24 +0000 [thread overview]
Message-ID: <20221031133624.E9DA8385DC0D@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/894
Build state: failed compile (failure)
Revision: ef07be453e0edf2f43034fcbc0581f61e630993e
Worker: bb2-1
Build Reason: (unknown)
Blamelist: Bruno Larsen <blarsen@redhat.com>, Cui, Lili <lili.cui@intel.com>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/894/steps/1/logs/stdio
- 2: rm -rf binutils-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/894/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/894/steps/3/logs/stdio
- 4: make ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/894/steps/4/logs/stdio
- warnings (6): https://builder.sourceware.org/buildbot/#builders/68/builds/894/steps/4/logs/warnings__6_
A new failure has been detected on builder binutils-fedora-x86_64 while building binutils-gdb.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/77/builds/878
Build state: failed compile (failure)
Revision: ef07be453e0edf2f43034fcbc0581f61e630993e
Worker: bb2-2
Build Reason: (unknown)
Blamelist: Bruno Larsen <blarsen@redhat.com>, Cui, Lili <lili.cui@intel.com>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/77/builds/878/steps/1/logs/stdio
- 2: rm -rf binutils-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/77/builds/878/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/77/builds/878/steps/3/logs/stdio
- 4: make ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/77/builds/878/steps/4/logs/stdio
- warnings (6): https://builder.sourceware.org/buildbot/#builders/77/builds/878/steps/4/logs/warnings__6_
A new failure has been detected on builder binutils-opensuseleap-x86_64 while building binutils-gdb.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/93/builds/760
Build state: failed compile (failure)
Revision: ef07be453e0edf2f43034fcbc0581f61e630993e
Worker: bb2-1
Build Reason: (unknown)
Blamelist: Bruno Larsen <blarsen@redhat.com>, Cui, Lili <lili.cui@intel.com>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/93/builds/760/steps/1/logs/stdio
- 2: rm -rf binutils-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/93/builds/760/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/93/builds/760/steps/3/logs/stdio
- 4: make ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/93/builds/760/steps/4/logs/stdio
- warnings (6): https://builder.sourceware.org/buildbot/#builders/93/builds/760/steps/4/logs/warnings__6_
A new failure has been detected on builder binutils-opensusetw-x86_64 while building binutils-gdb.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/102/builds/758
Build state: failed compile (failure)
Revision: ef07be453e0edf2f43034fcbc0581f61e630993e
Worker: bb1-2
Build Reason: (unknown)
Blamelist: Bruno Larsen <blarsen@redhat.com>, Cui, Lili <lili.cui@intel.com>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/102/builds/758/steps/1/logs/stdio
- 2: rm -rf binutils-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/102/builds/758/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/102/builds/758/steps/3/logs/stdio
- 4: make ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/102/builds/758/steps/4/logs/stdio
- warnings (7): https://builder.sourceware.org/buildbot/#builders/102/builds/758/steps/4/logs/warnings__7_
A new failure has been detected on builder binutils-rawhide-x86_64 while building binutils-gdb.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/133/builds/613
Build state: failed compile (failure)
Revision: ef07be453e0edf2f43034fcbc0581f61e630993e
Worker: bb2-2
Build Reason: (unknown)
Blamelist: Bruno Larsen <blarsen@redhat.com>, Cui, Lili <lili.cui@intel.com>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/133/builds/613/steps/1/logs/stdio
- 2: rm -rf binutils-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/133/builds/613/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/133/builds/613/steps/3/logs/stdio
- 4: make ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/133/builds/613/steps/4/logs/stdio
- warnings (8): https://builder.sourceware.org/buildbot/#builders/133/builds/613/steps/4/logs/warnings__8_
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/601
Build state: failed compile (failure)
Revision: ef07be453e0edf2f43034fcbc0581f61e630993e
Worker: bb2-2
Build Reason: (unknown)
Blamelist: Bruno Larsen <blarsen@redhat.com>, Cui, Lili <lili.cui@intel.com>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/149/builds/601/steps/1/logs/stdio
- 2: rm -rf binutils-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/149/builds/601/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/149/builds/601/steps/3/logs/stdio
- 4: make ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/149/builds/601/steps/4/logs/stdio
- warnings (6): https://builder.sourceware.org/buildbot/#builders/149/builds/601/steps/4/logs/warnings__6_
next reply other threads:[~2022-10-31 13:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 13:36 builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-09 23:57 builder
2023-01-09 23:46 builder
2022-12-16 12:24 builder
2022-12-12 9:54 builder
2022-12-07 4:25 builder
2022-12-05 0:18 builder
2022-11-30 16:24 builder
2022-11-30 16:21 builder
2022-11-11 6:30 builder
2022-11-01 9:58 builder
2022-10-19 9:14 builder
2022-07-08 10:24 builder
2022-06-27 11:11 builder
2022-06-21 10:32 builder
2022-06-21 16:40 ` Mark Wielaard
2022-06-13 8:13 builder
2022-06-13 8:18 ` Mark Wielaard
2022-06-13 9:08 ` Jan Beulich
2022-06-09 0:20 builder
[not found] ` <CAG_eJLfRrgsK62e7UX_HF7p5O+czBnTm6z+8K=KnDsasadkp5Q@mail.gmail.com>
2022-06-09 3:36 ` Mark Wielaard
2022-06-02 11:05 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=20221031133624.E9DA8385DC0D@sourceware.org \
--to=builder@sourceware.org \
--cc=binutils@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).