From: builder@sourceware.org
To: gcc-rust@gcc.gnu.org
Subject: ☝ Buildbot (Sourceware): gccrust - retry lost connection (master)
Date: Fri, 12 Apr 2024 01:13:09 +0000 [thread overview]
Message-ID: <20240412011309.270A93858D33@sourceware.org> (raw)
A retry build has been detected on builder gccrust-fedora-x86_64 while building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2601
Build state: retry lost connection
Revision: 96e4e5d27ec49416148b9a22a6c9bb050d562401
Worker: bb1-2
Build Reason: (unknown)
Blamelist: Owen Avery <powerboat9.gamer@gmail.com>, Pierre-Emmanuel Patry <pierre-emmanuel.patry@embecosm.com>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/16/builds/2601/steps/1/logs/stdio
- 2: rm -rf gccrs-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/16/builds/2601/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/16/builds/2601/steps/3/logs/stdio
- config.log: https://builder.sourceware.org/buildbot/#/builders/16/builds/2601/steps/3/logs/config_log
- 4: make ( warnings )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/16/builds/2601/steps/4/logs/stdio
- warnings (40): https://builder.sourceware.org/buildbot/#/builders/16/builds/2601/steps/4/logs/warnings__40_
- 5: make check ( warnings )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/16/builds/2601/steps/5/logs/stdio
- rust.sum: https://builder.sourceware.org/buildbot/#/builders/16/builds/2601/steps/5/logs/rust_sum
- rust.log: https://builder.sourceware.org/buildbot/#/builders/16/builds/2601/steps/5/logs/rust_log
- warnings (6): https://builder.sourceware.org/buildbot/#/builders/16/builds/2601/steps/5/logs/warnings__6_
- 6: grep FAIL or unexpected rust.sum ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/16/builds/2601/steps/6/logs/stdio
- 7: prep ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/16/builds/2601/steps/7/logs/stdio
- 8: build bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/16/builds/2601/steps/8/logs/stdio
- 9: fetch bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/16/builds/2601/steps/9/logs/stdio
- 10: unpack bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/16/builds/2601/steps/10/logs/stdio
- 11: pass .bunsen.source.gitname ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/16/builds/2601/steps/11/logs/stdio
- 12: pass .bunsen.source.gitdescribe ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/16/builds/2601/steps/12/logs/stdio
reply other threads:[~2024-04-12 1:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240412011309.270A93858D33@sourceware.org \
--to=builder@sourceware.org \
--cc=gcc-rust@gcc.gnu.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).