From: builder@sourceware.org
To: "Philip Herron" <philip.herron@embecosm.com>, bors@sourceware.org
Cc: gcc-rust@gcc.gnu.org
Subject: ☝ Buildbot (GNU Toolchain): gccrust - retry lost connection compile (retry) (master)
Date: Thu, 21 Apr 2022 19:53:12 +0000 [thread overview]
Message-ID: <20220421195312.7EA643858D37@sourceware.org> (raw)
A retry build has been detected on builder gccrust-debian-arm64 while building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/34/builds/10
Build state: retry lost connection compile (retry)
Revision: 53ce1d5ac9106bc7427f14c285d782c1023124ec
Worker: debian-arm64
Build Reason: (unknown)
Blamelist: Philip Herron <philip.herron@embecosm.com>, bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/34/builds/10/steps/1/logs/stdio
- 2: rm -rf gccrs-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/34/builds/10/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/34/builds/10/steps/3/logs/stdio
- 4: make ( retry )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/34/builds/10/steps/4/logs/stdio
- cancelled: https://builder.sourceware.org/buildbot/#builders/34/builds/10/steps/4/logs/cancelled
A restored build has been detected on builder gccrust-debian-arm64 while building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/34/builds/12
Build state: build successful
Revision: 53ce1d5ac9106bc7427f14c285d782c1023124ec
Worker: debian-arm64
Build Reason: (unknown)
Blamelist: Philip Herron <philip.herron@embecosm.com>, bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/34/builds/12/steps/1/logs/stdio
- 2: rm -rf gccrs-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/34/builds/12/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/34/builds/12/steps/3/logs/stdio
- 4: make ( warnings )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/34/builds/12/steps/4/logs/stdio
- warnings (76): https://builder.sourceware.org/buildbot/#builders/34/builds/12/steps/4/logs/warnings__76_
- 5: make check ( warnings )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/34/builds/12/steps/5/logs/stdio
- rust.sum: https://builder.sourceware.org/buildbot/#builders/34/builds/12/steps/5/logs/rust_sum
- rust.log: https://builder.sourceware.org/buildbot/#builders/34/builds/12/steps/5/logs/rust_log
- warnings (1): https://builder.sourceware.org/buildbot/#builders/34/builds/12/steps/5/logs/warnings__1_
- 6: grep unexpected rust.sum ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/34/builds/12/steps/6/logs/stdio
next reply other threads:[~2022-04-21 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 19:53 builder [this message]
2022-08-25 16:24 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=20220421195312.7EA643858D37@sourceware.org \
--to=builder@sourceware.org \
--cc=bors@sourceware.org \
--cc=gcc-rust@gcc.gnu.org \
--cc=philip.herron@embecosm.com \
/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).