From: builder@sourceware.org
To: binutils@sourceware.org
Subject: ☝ Buildbot (Sourceware): binutils-gdb - retry lost connection test (exception) (master)
Date: Fri, 15 Mar 2024 11:01:32 +0000 [thread overview]
Message-ID: <20240315110132.E82143857B86@sourceware.org> (raw)
A retry build 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/3253
Build state: retry lost connection test (exception)
Revision: 9fe07b7f95fbfdaf34d5b69e6d73cae000b43eea
Worker: bb2-1
Build Reason: (unknown)
Blamelist: Jan Beulich <jbeulich@suse.com>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/133/builds/3253/steps/1/logs/stdio
- 2: rm -rf binutils-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/133/builds/3253/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/133/builds/3253/steps/3/logs/stdio
- config.log: https://builder.sourceware.org/buildbot/#/builders/133/builds/3253/steps/3/logs/config_log
- 4: make ( warnings )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/133/builds/3253/steps/4/logs/stdio
- warnings (72): https://builder.sourceware.org/buildbot/#/builders/133/builds/3253/steps/4/logs/warnings__72_
- 5: make check ( exception )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/133/builds/3253/steps/5/logs/stdio
- ld.sum: https://builder.sourceware.org/buildbot/#/builders/133/builds/3253/steps/5/logs/ld_sum
- ld.log: https://builder.sourceware.org/buildbot/#/builders/133/builds/3253/steps/5/logs/ld_log
- gas.sum: https://builder.sourceware.org/buildbot/#/builders/133/builds/3253/steps/5/logs/gas_sum
- gas.log: https://builder.sourceware.org/buildbot/#/builders/133/builds/3253/steps/5/logs/gas_log
- binutils.sum: https://builder.sourceware.org/buildbot/#/builders/133/builds/3253/steps/5/logs/binutils_sum
- binutils.log: https://builder.sourceware.org/buildbot/#/builders/133/builds/3253/steps/5/logs/binutils_log
- libsframe.sum: https://builder.sourceware.org/buildbot/#/builders/133/builds/3253/steps/5/logs/libsframe_sum
- libsframe.log: https://builder.sourceware.org/buildbot/#/builders/133/builds/3253/steps/5/logs/libsframe_log
- libctf.sum: https://builder.sourceware.org/buildbot/#/builders/133/builds/3253/steps/5/logs/libctf_sum
- libctf.log: https://builder.sourceware.org/buildbot/#/builders/133/builds/3253/steps/5/logs/libctf_log
- cancelled: https://builder.sourceware.org/buildbot/#/builders/133/builds/3253/steps/5/logs/cancelled
- warnings (15): https://builder.sourceware.org/buildbot/#/builders/133/builds/3253/steps/5/logs/warnings__15_
next reply other threads:[~2024-03-15 11:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 11:01 builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-19 3:34 builder
2024-04-11 13:27 builder
2024-03-28 1:22 builder
2024-02-02 10:18 builder
2024-02-02 9:29 builder
2024-01-19 10:51 builder
2023-06-28 9:33 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=20240315110132.E82143857B86@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).