From: builder@sourceware.org
To: gcc-rust@gcc.gnu.org
Subject: ☠ Buildbot (Sourceware): gccrust - failed 'grep unexpected ...' (failure) (master)
Date: Mon, 08 May 2023 16:09:20 +0000 [thread overview]
Message-ID: <20230508160920.2F0DF3858D32@sourceware.org> (raw)
A new failure has been detected on builder gccrust-debian-i386 while building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/27/builds/1213
Build state: failed 'grep unexpected ...' (failure)
Revision: ea597e73da52a4292986b5267fc535006ae4c343
Worker: debian-i386-2
Build Reason: (unknown)
Blamelist: Philip Herron <herron.philip@googlemail.com>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/1213/steps/1/logs/stdio
- 2: rm -rf gccrs-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/1213/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/1213/steps/3/logs/stdio
- config.log: https://builder.sourceware.org/buildbot/#builders/27/builds/1213/steps/3/logs/config_log
- 4: make ( warnings )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/1213/steps/4/logs/stdio
- warnings (32): https://builder.sourceware.org/buildbot/#builders/27/builds/1213/steps/4/logs/warnings__32_
- 5: make check ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/1213/steps/5/logs/stdio
- rust.sum: https://builder.sourceware.org/buildbot/#builders/27/builds/1213/steps/5/logs/rust_sum
- rust.log: https://builder.sourceware.org/buildbot/#builders/27/builds/1213/steps/5/logs/rust_log
- 6: grep unexpected rust.sum ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/1213/steps/6/logs/stdio
- 7: prep ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/1213/steps/7/logs/stdio
- 8: build bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/1213/steps/8/logs/stdio
- 9: fetch bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/1213/steps/9/logs/stdio
- 10: unpack bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/1213/steps/10/logs/stdio
- 11: pass .bunsen.source.gitname ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/1213/steps/11/logs/stdio
- 12: pass .bunsen.source.gitdescribe ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/1213/steps/12/logs/stdio
- 13: pass .bunsen.source.gitbranch ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/1213/steps/13/logs/stdio
- 14: pass .bunsen.source.gitrepo ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/1213/steps/14/logs/stdio
- 15: upload to bunsen ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/1213/steps/15/logs/stdio
- 16: clean up ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/1213/steps/16/logs/stdio
- 17: rm -rf gccrs-build_1 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/1213/steps/17/logs/stdio
next reply other threads:[~2023-05-08 16:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 16:09 builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-12 20:38 builder
2023-08-10 11:05 builder
2023-07-12 10:49 builder
2023-07-09 12:58 builder
2023-06-22 10:58 builder
2023-05-17 22:46 builder
2023-04-11 14:12 builder
2023-04-05 11:16 builder
2023-04-05 11:04 builder
2023-03-04 22:29 builder
2023-03-02 20:53 builder
2023-03-01 15:59 builder
2023-03-01 16:50 ` Thomas Schwinge
2023-02-13 21:22 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=20230508160920.2F0DF3858D32@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).