public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: builder@sourceware.org
To: gdb-testers@sourceware.org
Subject: ☝ Buildbot (Sourceware): binutils-gdb - retry lost connection Ran (exception) (master)
Date: Wed, 10 Jan 2024 12:32:57 +0000 [thread overview]
Message-ID: <20240110123257.75A203858C41@sourceware.org> (raw)
A retry build has been detected on builder gdb-fedora-sanitize-x86_64 while building binutils-gdb.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/267/builds/839
Build state: retry lost connection Ran (exception)
Revision: 862180a2d10963494356ec089a16b808bab736bd
Worker: bb2-1
Build Reason: (unknown)
Blamelist: Tom Tromey <tromey@adacore.com>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/1/logs/stdio
- 2: rm -rf gdb-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/3/logs/stdio
- config.log: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/3/logs/config_log
- 4: make ( warnings )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/4/logs/stdio
- warnings (20): https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/4/logs/warnings__20_
- 5: make check-gdb ( warnings )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/5/logs/stdio
- gdb.sum: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/5/logs/gdb_sum
- gdb.log: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/5/logs/gdb_log
- warnings (1): https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/5/logs/warnings__1_
- 6: prep ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/6/logs/stdio
- 7: build bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/7/logs/stdio
- 8: fetch bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/8/logs/stdio
- 9: unpack bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/9/logs/stdio
- 10: pass .bunsen.source.gitname ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/10/logs/stdio
- 11: pass .bunsen.source.gitdescribe ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/11/logs/stdio
- 12: pass .bunsen.source.gitbranch ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/12/logs/stdio
- 13: pass .bunsen.source.gitrepo ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/13/logs/stdio
- 14: upload to bunsen ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/14/logs/stdio
- 15: clean up ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/15/logs/stdio
- 16: make check-gdb_1 ( warnings )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/16/logs/stdio
- gdb.sum: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/16/logs/gdb_sum
- gdb.log: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/16/logs/gdb_log
- warnings (1): https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/16/logs/warnings__1_
- 17: prep_1 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/17/logs/stdio
- 18: build bunsen.cpio.gz_1 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/18/logs/stdio
- 19: fetch bunsen.cpio.gz_1 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/19/logs/stdio
- 20: unpack bunsen.cpio.gz_1 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/20/logs/stdio
- 21: pass .bunsen.source.gitname_1 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/21/logs/stdio
- 22: pass .bunsen.source.gitdescribe_1 ( exception )
Logs:
- cancelled: https://builder.sourceware.org/buildbot/#/builders/267/builds/839/steps/22/logs/cancelled
next reply other threads:[~2024-01-10 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 12:32 builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-10 1:36 builder
2024-02-29 11:31 builder
2024-01-02 15: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=20240110123257.75A203858C41@sourceware.org \
--to=builder@sourceware.org \
--cc=gdb-testers@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).