From: builder@sourceware.org
To: binutils@sourceware.org
Subject: ☝ Buildbot (Sourceware): binutils-gdb - retry lost connection test (retry) (master)
Date: Thu, 28 Sep 2023 20:41:59 +0000 [thread overview]
Message-ID: <20230928204159.3A9523858C52@sourceware.org> (raw)
A retry build 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/2765
Build state: retry lost connection test (retry)
Revision: 1a64c35996054f06a951edc1d22a85ee20ddda07
Worker: bb1-1
Build Reason: (unknown)
Blamelist: Andrew Burgess <aburgess@redhat.com>, Michael J. Eager <eager@eagercon.com>, Simon Marchi <simon.marchi@polymtl.ca>, Tom Tromey <tromey@adacore.com>, Tom de Vries <tdevries@suse.de>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/2765/steps/1/logs/stdio
- 2: rm -rf binutils-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/2765/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/2765/steps/3/logs/stdio
- config.log: https://builder.sourceware.org/buildbot/#builders/68/builds/2765/steps/3/logs/config_log
- 4: make ( warnings )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/2765/steps/4/logs/stdio
- warnings (20): https://builder.sourceware.org/buildbot/#builders/68/builds/2765/steps/4/logs/warnings__20_
- 5: make check ( retry )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/2765/steps/5/logs/stdio
- ld.sum: https://builder.sourceware.org/buildbot/#builders/68/builds/2765/steps/5/logs/ld_sum
- ld.log: https://builder.sourceware.org/buildbot/#builders/68/builds/2765/steps/5/logs/ld_log
- gas.sum: https://builder.sourceware.org/buildbot/#builders/68/builds/2765/steps/5/logs/gas_sum
- gas.log: https://builder.sourceware.org/buildbot/#builders/68/builds/2765/steps/5/logs/gas_log
- binutils.sum: https://builder.sourceware.org/buildbot/#builders/68/builds/2765/steps/5/logs/binutils_sum
- binutils.log: https://builder.sourceware.org/buildbot/#builders/68/builds/2765/steps/5/logs/binutils_log
- libsframe.sum: https://builder.sourceware.org/buildbot/#builders/68/builds/2765/steps/5/logs/libsframe_sum
- libsframe.log: https://builder.sourceware.org/buildbot/#builders/68/builds/2765/steps/5/logs/libsframe_log
- cancelled: https://builder.sourceware.org/buildbot/#builders/68/builds/2765/steps/5/logs/cancelled
A retry build 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/2766
Build state: worker not available
Revision: (unknown)
Worker: bb1-1
Build Reason: (unknown)
Blamelist: Andrew Burgess <aburgess@redhat.com>, Michael J. Eager <eager@eagercon.com>, Simon Marchi <simon.marchi@polymtl.ca>, Tom Tromey <tromey@adacore.com>, Tom de Vries <tdevries@suse.de>
Steps:
- 0: worker_preparation ( exception )
Logs:
- err.text: https://builder.sourceware.org/buildbot/#builders/68/builds/2766/steps/0/logs/err_text
- err.html: https://builder.sourceware.org/buildbot/#builders/68/builds/2766/steps/0/logs/err_html
A retry build 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/2626
Build state: retry lost connection compile (retry)
Revision: 1a64c35996054f06a951edc1d22a85ee20ddda07
Worker: bb1-2
Build Reason: (unknown)
Blamelist: Andrew Burgess <aburgess@redhat.com>, Michael J. Eager <eager@eagercon.com>, Simon Marchi <simon.marchi@polymtl.ca>, Tom Tromey <tromey@adacore.com>, Tom de Vries <tdevries@suse.de>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/93/builds/2626/steps/1/logs/stdio
- 2: rm -rf binutils-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/93/builds/2626/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/93/builds/2626/steps/3/logs/stdio
- config.log: https://builder.sourceware.org/buildbot/#builders/93/builds/2626/steps/3/logs/config_log
- 4: make ( retry )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/93/builds/2626/steps/4/logs/stdio
- cancelled: https://builder.sourceware.org/buildbot/#builders/93/builds/2626/steps/4/logs/cancelled
A retry build 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/2627
Build state: worker not available
Revision: (unknown)
Worker: bb1-2
Build Reason: (unknown)
Blamelist: Andrew Burgess <aburgess@redhat.com>, Michael J. Eager <eager@eagercon.com>, Simon Marchi <simon.marchi@polymtl.ca>, Tom Tromey <tromey@adacore.com>, Tom de Vries <tdevries@suse.de>
Steps:
- 0: worker_preparation ( exception )
Logs:
- err.text: https://builder.sourceware.org/buildbot/#builders/93/builds/2627/steps/0/logs/err_text
- err.html: https://builder.sourceware.org/buildbot/#builders/93/builds/2627/steps/0/logs/err_html
next reply other threads:[~2023-09-28 20:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 20:41 builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-19 3:36 builder
2024-01-19 12:05 builder
2023-10-19 4:56 builder
2023-09-29 16:51 builder
2023-09-29 16:13 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=20230928204159.3A9523858C52@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).