From: builder@sourceware.org
To: binutils@sourceware.org
Subject: ☝ Buildbot (Sourceware): binutils-gdb - retry lost connection test (retry) (master)
Date: Fri, 19 Jan 2024 12:05:48 +0000 [thread overview]
Message-ID: <20240119120548.5E2353858C56@sourceware.org> (raw)
A retry build 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/3349
Build state: retry lost connection test (retry)
Revision: 2519809009ed5e250ad9ed9b6184d9c45dba5029
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/77/builds/3349/steps/1/logs/stdio
- 2: rm -rf binutils-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/77/builds/3349/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/77/builds/3349/steps/3/logs/stdio
- config.log: https://builder.sourceware.org/buildbot/#/builders/77/builds/3349/steps/3/logs/config_log
- 4: make ( warnings )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/77/builds/3349/steps/4/logs/stdio
- warnings (67): https://builder.sourceware.org/buildbot/#/builders/77/builds/3349/steps/4/logs/warnings__67_
- 5: make check ( retry )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/77/builds/3349/steps/5/logs/stdio
- ld.sum: https://builder.sourceware.org/buildbot/#/builders/77/builds/3349/steps/5/logs/ld_sum
- ld.log: https://builder.sourceware.org/buildbot/#/builders/77/builds/3349/steps/5/logs/ld_log
- gas.sum: https://builder.sourceware.org/buildbot/#/builders/77/builds/3349/steps/5/logs/gas_sum
- gas.log: https://builder.sourceware.org/buildbot/#/builders/77/builds/3349/steps/5/logs/gas_log
- binutils.sum: https://builder.sourceware.org/buildbot/#/builders/77/builds/3349/steps/5/logs/binutils_sum
- binutils.log: https://builder.sourceware.org/buildbot/#/builders/77/builds/3349/steps/5/logs/binutils_log
- libsframe.sum: https://builder.sourceware.org/buildbot/#/builders/77/builds/3349/steps/5/logs/libsframe_sum
- libsframe.log: https://builder.sourceware.org/buildbot/#/builders/77/builds/3349/steps/5/logs/libsframe_log
- libctf.sum: https://builder.sourceware.org/buildbot/#/builders/77/builds/3349/steps/5/logs/libctf_sum
- libctf.log: https://builder.sourceware.org/buildbot/#/builders/77/builds/3349/steps/5/logs/libctf_log
- cancelled: https://builder.sourceware.org/buildbot/#/builders/77/builds/3349/steps/5/logs/cancelled
next reply other threads:[~2024-01-19 12:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 12:05 builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-19 3:36 builder
2023-10-19 4:56 builder
2023-09-29 16:51 builder
2023-09-29 16:13 builder
2023-09-28 20:41 builder
2023-09-01 11:17 builder
2023-09-01 11:25 ` Sam James
2023-09-02 14:27 ` Mark Wielaard
2023-07-31 9:35 builder
2023-07-31 9:21 builder
2023-07-24 5:03 builder
2023-06-16 4:45 builder
2023-06-15 3:16 builder
2023-05-12 10:50 builder
2023-03-30 21:39 builder
2023-02-17 1:11 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=20240119120548.5E2353858C56@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).