From: builder@sourceware.org
To: gcc-rust@gcc.gnu.org
Subject: ☠ Buildbot (GNU Toolchain): gccrust - failed 'make clean' (failure) (master)
Date: Thu, 21 Jul 2022 22:38:18 +0000 [thread overview]
Message-ID: <20220721223818.B15B538356A7@sourceware.org> (raw)
A new failure has been detected on builder gccrust-bootstrap-debian-amd64 while building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/107/builds/43
Build state: failed 'make clean' (failure)
Revision: 51f03d9d697b0f3fed65f85e88ce41d424c844fb
Worker: bb2
Build Reason: (unknown)
Blamelist: Thomas Schwinge <thomas@codesourcery.com>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/1/logs/stdio
- 2: rm -rf gccrs-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/3/logs/stdio
- 4: make ( warnings )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/4/logs/stdio
- warnings (42): https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/4/logs/warnings__42_
- 5: make check ( warnings )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/5/logs/stdio
- rust.sum: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/5/logs/rust_sum
- rust.log: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/5/logs/rust_log
- warnings (1): https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/5/logs/warnings__1_
- 6: grep unexpected rust.sum ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/6/logs/stdio
- 7: prep ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/7/logs/stdio
- 8: build bunsen.cpio ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/8/logs/stdio
- 9: fetch bunsen.cpio ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/9/logs/stdio
- 10: unpack bunsen.cpio ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/10/logs/stdio
- 11: pass .bunsen.source.gitname ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/11/logs/stdio
- 12: pass .bunsen.source.gitbranch ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/12/logs/stdio
- 13: pass .bunsen.source.gitrepo ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/13/logs/stdio
- 14: upload to bunsen ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/14/logs/stdio
- 15: clean up ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/15/logs/stdio
- 16: make clean ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/107/builds/43/steps/16/logs/stdio
next reply other threads:[~2022-07-21 22:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 22:38 builder [this message]
2022-07-21 22:49 ` Mark Wielaard
2022-07-22 14:48 ` Mark Wielaard
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=20220721223818.B15B538356A7@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).