public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: <gcc-rust@gcc.gnu.org>, <mxlol233@outlook.com>
Subject: Re: ☠ Buildbot (Sourceware): gccrust - failed 'grep unexpected ...' (failure) (master)
Date: Wed, 1 Mar 2023 17:50:39 +0100	[thread overview]
Message-ID: <87cz5s5sbk.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <20230301155932.B1C953858D33@sourceware.org>

Hi!

On 2023-03-01T15:59:32+0000, builder--- via Gcc-rust <gcc-rust@gcc.gnu.org> wrote:
> 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/893

I've filed <https://github.com/Rust-GCC/gccrs/issues/1952>
'ICE with #1929 commit 9c46a853be4b5a9c2e1b965fa0dcd44beed71924 "Add feature gate definition for extern_types"'.


Grüße
 Thomas


> Build state: failed 'grep unexpected ...' (failure)
> Revision: 9c46a853be4b5a9c2e1b965fa0dcd44beed71924
> Worker: debian-i386-2
> Build Reason: (unknown)
> Blamelist: mxlol233 <mxlol233@outlook.com>
>
> Steps:
>
> - 0: worker_preparation ( success )
>
> - 1: git checkout ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/893/steps/1/logs/stdio
>
> - 2: rm -rf gccrs-build ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/893/steps/2/logs/stdio
>
> - 3: configure ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/893/steps/3/logs/stdio
>         - config.log: https://builder.sourceware.org/buildbot/#builders/27/builds/893/steps/3/logs/config_log
>
> - 4: make ( warnings )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/893/steps/4/logs/stdio
>         - warnings (29): https://builder.sourceware.org/buildbot/#builders/27/builds/893/steps/4/logs/warnings__29_
>
> - 5: make check ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/893/steps/5/logs/stdio
>         - rust.sum: https://builder.sourceware.org/buildbot/#builders/27/builds/893/steps/5/logs/rust_sum
>         - rust.log: https://builder.sourceware.org/buildbot/#builders/27/builds/893/steps/5/logs/rust_log
>
> - 6: grep unexpected rust.sum ( failure )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/893/steps/6/logs/stdio
>
> - 7: prep ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/893/steps/7/logs/stdio
>
> - 8: build bunsen.cpio.gz ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/893/steps/8/logs/stdio
>
> - 9: fetch bunsen.cpio.gz ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/893/steps/9/logs/stdio
>
> - 10: unpack bunsen.cpio.gz ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/893/steps/10/logs/stdio
>
> - 11: pass .bunsen.source.gitname ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/893/steps/11/logs/stdio
>
> - 12: pass .bunsen.source.gitdescribe ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/893/steps/12/logs/stdio
>
> - 13: pass .bunsen.source.gitbranch ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/893/steps/13/logs/stdio
>
> - 14: pass .bunsen.source.gitrepo ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/893/steps/14/logs/stdio
>
> - 15: upload to bunsen ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/893/steps/15/logs/stdio
>
> - 16: clean up ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/893/steps/16/logs/stdio
>
> - 17: rm -rf gccrs-build_1 ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/27/builds/893/steps/17/logs/stdio
>
> --
> Gcc-rust mailing list
> Gcc-rust@gcc.gnu.org
> https://gcc.gnu.org/mailman/listinfo/gcc-rust
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955

  reply	other threads:[~2023-03-01 16:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 15:59 builder
2023-03-01 16:50 ` Thomas Schwinge [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-05-08 16:09 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-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=87cz5s5sbk.fsf@euler.schwinge.homeip.net \
    --to=thomas@codesourcery.com \
    --cc=gcc-rust@gcc.gnu.org \
    --cc=mxlol233@outlook.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).