public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: builder@sourceware.org
To: gcc-rust@gcc.gnu.org
Subject: ☠ Buildbot (GNU Toolchain): gccrust - failed 'grep unexpected ...' (failure) (master)
Date: Fri, 30 Sep 2022 16:21:43 +0000	[thread overview]
Message-ID: <20220930162143.A60D33858C55@sourceware.org> (raw)

A new failure has been detected on builder gccrust-fedora-ppc64le while building gccrust.

Full details are available at:
    https://builder.sourceware.org/buildbot/#builders/19/builds/390

Build state: failed 'grep unexpected ...' (failure)
Revision: d1069815fa6238712f51a23dfd43d2ae6cd7c5e8
Worker: fedora-ppc64le
Build Reason: (unknown)
Blamelist: Aldy Hernandez <aldyh@redhat.com>, Boris Yakobowski <yakobowski@adacore.com>, Eric Botcazou <ebotcazou@adacore.com>, GCC Administrator <gccadmin@gcc.gnu.org>, Ghjuvan Lacambre <lacambre@adacore.com>, Harald Anlauf <anlauf@gmx.de>, Hu, Lin1 <lin1.hu@intel.com>, Iain Buclaw <ibuclaw@gdcproject.org>, Jakub Jelinek <jakub@redhat.com>, Jeff Law <jeffreyalaw@gmail.com>, Jeff Law <jlaw@ventanamicro.com>, Jonathan Wakely <jwakely@redhat.com>, Justin Squirek <squirek@adacore.com>, Kewen Lin <linkw@linux.ibm.com>, Kyrylo Tkachov <kyrylo.tkachov@arm.com>, Kévin Le Gouguec <legouguec@adacore.com>, Marek Polacek <polacek@redhat.com>, Martin Liska <mliska@suse.cz>, Meghan Denny <hello@nektro.net>, Mikael Morin <mikael@gcc.gnu.org>, Patrick Palka <ppalka@redhat.com>, Philip Herron <philip.herron@embecosm.com>, Piotr Trojanek <trojanek@adacore.com>, Steve Baird <baird@adacore.com>, Thomas Neumann <tneumann@users.sourceforge.net>, Thomas Schwinge <thomas@codesourcery.com>, Tobias Burnus <tobias@codesourcery.com>, Torbjörn SVENSSON <torbjorn.svensson@foss.st.com>, Tucker Taft <taft@adacore.com>, bors[bot] <26634292+bors[bot]@users.noreply.github.com>, liuhongt <hongtao.liu@intel.com>

Steps:

- 0: worker_preparation ( success )

- 1: git checkout ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/390/steps/1/logs/stdio

- 2: rm -rf gccrs-build ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/390/steps/2/logs/stdio

- 3: configure ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/390/steps/3/logs/stdio

- 4: make ( warnings )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/390/steps/4/logs/stdio
        - warnings (29): https://builder.sourceware.org/buildbot/#builders/19/builds/390/steps/4/logs/warnings__29_

- 5: make check ( warnings )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/390/steps/5/logs/stdio
        - rust.sum: https://builder.sourceware.org/buildbot/#builders/19/builds/390/steps/5/logs/rust_sum
        - rust.log: https://builder.sourceware.org/buildbot/#builders/19/builds/390/steps/5/logs/rust_log
        - warnings (4): https://builder.sourceware.org/buildbot/#builders/19/builds/390/steps/5/logs/warnings__4_

- 6: grep unexpected rust.sum ( failure )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/390/steps/6/logs/stdio

- 7: prep ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/390/steps/7/logs/stdio

- 8: build bunsen.cpio.gz ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/390/steps/8/logs/stdio

- 9: fetch bunsen.cpio.gz ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/390/steps/9/logs/stdio

- 10: unpack bunsen.cpio.gz ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/390/steps/10/logs/stdio

- 11: pass .bunsen.source.gitname ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/390/steps/11/logs/stdio

- 12: pass .bunsen.source.gitdescribe ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/390/steps/12/logs/stdio

- 13: pass .bunsen.source.gitbranch ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/390/steps/13/logs/stdio

- 14: pass .bunsen.source.gitrepo ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/390/steps/14/logs/stdio

- 15: upload to bunsen ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/390/steps/15/logs/stdio

- 16: clean up ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/390/steps/16/logs/stdio

- 17: rm -rf gccrs-build_1 ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#builders/19/builds/390/steps/17/logs/stdio


             reply	other threads:[~2022-09-30 16:21 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30 16:21 builder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-09 11:17 builder
2022-12-07 15:50 builder
2022-12-07 15:47 builder
2022-11-30 10:53 builder
2022-11-07 14:09 builder
2022-10-27 19:59 builder
2022-10-26 16:25 builder
2022-10-21 16:03 builder
2022-09-27  7:02 builder
2022-09-27  6:49 builder
2022-08-31 10:44 builder
2022-08-25 16:37 builder
2022-08-22 15:30 builder
2022-08-19 15:07 builder
2022-08-17 12:54 builder
2022-08-09 15:36 builder
2022-08-09 15:33 builder
2022-08-09 14:53 builder
2022-08-05 13:57 builder
2022-08-05 10:37 builder
2022-08-04 20:34 builder
2022-07-22 11:58 builder
2022-07-15 17:46 builder
2022-07-15 19:18 ` Mark Wielaard
2022-07-07 10:34 builder
2022-06-01  9:33 builder
2022-05-26  9:53 builder
2022-05-26 13:15 ` Mark Wielaard
2022-05-19 10:43 builder
2022-05-11 18:06 builder
2022-05-11 18:30 ` Mark Wielaard
2022-05-10 18:05 builder
2022-05-10 11:00 builder
2022-05-10 11:38 ` Mark Wielaard
2022-05-10 12:18 ` dkm
2022-05-09 11:33 builder
2022-04-28 19:48 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=20220930162143.A60D33858C55@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).